COMMUNICATION METHOD AND COMMUNICATIONS APPARATUS

专利摘要:
this application provides a communication method and a communications device in order to select a network slice based on a network slice deployment status. the method includes: sending, through a first network node, a first message to a second network node, where the first message includes a network slice identifier that corresponds to at least one network slice in a first set of slices network, the first set of network slices is a network slice that needs to be accessed by a terminal device, and the second network node is a first central network node or a second access network node; and receiving, by the first network node, a first response message sent by the second network node, wherein the first response message includes a network slice identifier that corresponds to at least one network slice in a second set of slices network, and the second set of network slices includes network slices that are used for access by the terminal device and that are determined, based on a status of a network slice supported by the second access network node, by the second node network or by a second central network node of a communications system to which the second access network node belongs.
公开号:BR112019015174A2
申请号:R112019015174-5
申请日:2018-01-25
公开日:2020-03-24
发明作者:Lou Chong；Wang Rui；Dai Mingzeng；Zeng Qinghai
申请人:Huawei Technologies Co., Ltd.；
IPC主号:

专利说明:

“COMMUNICATION METHOD, COMMUNICATIONS DEVICE, SYSTEM CHIP, COMPUTER PROGRAM PRODUCT, COMPUTER PROGRAM STORAGE MEDIA AND COMMUNICATION SYSTEM” [001] This application claims priority to Chinese Patent Application 201710062740.1, filed at the Office of Chinese Patents on January 25, 2017, and entitled “COMMUNICATION METHOD AND COMMUNICATION APPARATUS”, which is fully incorporated in this report as a reference.
TECHNICAL FIELD [002] This request refers to the communications field and, more specifically, a communication method and a communications device.
FUNDAMENTALS [003] In a fifth generation communication system (fifthgeneration, 5G), an NS network slice network architecture (Network slice, NS) is proposed to satisfy different needs of users.
[004] However, in a real network scenario, some network slices can be implemented only in a local area network. For example, a network slice is established in an industrial park or in a stadium to improve the user experience when a terminal device starts a service in the industrial park or in the stadium. If the terminal device needs to be transferred from a source cell to a destination cell, it is likely that the destination cell does not support a network slice that the terminal device needs to access. Therefore, a technology is required to select an appropriate network slice for the terminal device.
SUMMARY [005] This application provides a communication method and a communications device, in order to select a network slice for a terminal device with reference to a situation of a network slice supported by an access network device that will be accessed by the terminal device.
[006] According to a first aspect, a method of communication is provided. The communication method includes: sending, through a first network node, a first message to a second network node, where
Petition 870190077990, of 12/08/2019, p. 7/83
2/69 the first message includes a network slice identifier corresponding to at least one network slice in a first set of network slices, the network slice in the first set of network slices is a network slice that is selected for a terminal device and that is used for access by the terminal device, the first network node is a first access network node that is currently accessed by the terminal device, the second network node is a first main network node or a second node the access network to be accessed by the terminal device, and the first main network node is a main network node of a communication system to which the first network node belongs; and receiving, by the first network node, a first response message sent by the second network node, where the first response message includes a network slice identifier corresponding to at least one network slice in a second set of network slices ; the second set of network slices is a set of network slices that is used for access by the terminal device and that is determined by the second network node based on a situation of a network slice supported by the second access network node and the network slice identifier corresponding to at least one network slice in the first set of network slices, or the second set of network slices is a set of network slices that is used for access by the terminal device and which is determined by a second main network node based on a situation of a network slice supported by the second access network node and the network slice identifier corresponding to at least one network slice in the first set of network slices; and the second main network node is a main network node of a communication system to which the second access network node belongs.
[007] Therefore, according to the communication method in this modality of this request, the first network node sends the first message to the second network node, where the first message includes the network slice identifier corresponding to at least one slice in the first set of network slices. Based on the network slice identifier corresponding to at least one network slice in the first set of network slices included in the first message, the second network node can determine, with reference to the status of the network slice supported by the second network node access point, the network slice identifier corresponding to at least one network slice in the
Petition 870190077990, of 12/08/2019, p. 8/83
3/69 second set of network slices. Because the network slice identifier corresponding to at least one network slice in the second set of network slices is determined based on a situation of a network slice supported by the second node of the access network to be accessed by the device terminal, when the terminal device is transferred from the first node of the access network to the second node of the access network, the situation of the network slice supported by the second node of the access network can be considered to determine a network slice to be accessed to the terminal device, thereby ensuring smooth handover.
[008] Optionally, the first message can be a handover request message or, if the second network node is the second node in the access network, the first message can alternatively be another message used for communication between the first network node access point and the second node of the access network, or, if the second network node is the first main network node, the first message may alternatively be another message used for communication between the first node of the access network and the first node main network.
[009] Correspondingly, the first response message may be a handover request confirmation message or, if the second network node is the second node in the access network, the first response message may alternatively be another message used for communication. between the first node of the access network and the second node of the access network, or, if the second network node is the first main network node, the first reply message may alternatively be another message used for communication between the first node of the access network and the first main network node.
[010] In a possible implementation, the second set of network slices is determined by either the first main network node or the second main network node, the first response message still includes a first non-access layer NAS message, the first NAS message includes the network slice identifier corresponding to at least one network slice in the second set of network slices, and the first NAS message is used to instruct the terminal device to initiate a network slice reselection process .
Petition 870190077990, of 12/08/2019, p. 9/83
4/69 [011] Specifically, the second set of network slices can be determined by the main network node in the communications system to which the first network node belongs, that is, the first main network node. In this case, the first node of the access network and the second node of the access network belong to the same communications system. Alternatively, the second set of network slices can be determined by the main network node in the communications system to which the second access network node belongs, that is, the second main network node. When the first response message is determined by a main network node (the first main network node or the second main network node), the first response message can also include the first NAS message, where the first NAS message includes the network slice identifier corresponding to at least one network slice in the second set of network slices determined by the main network node. After receiving the first reply message including the first NAS message, the first network node can transmit the first NAS message to the terminal device, so that the terminal device can start the network slice reselection process after receive the first NAS message.
[012] In a possible implementation, the method also includes: sending, through the first node of the network, a second message to the terminal device, where the second message includes the first NAS message.
[013] Optionally, the second message can be a handover instruction, and the handover instruction can be used to deliver the terminal device from the first node in the access network to the second node in the access network.
[014] In a possible implementation, the method also includes: receiving, by the first network node, a third message sent by the terminal device or the first main network node, where the third message includes a network slice identifier corresponding to each network slice in the first set of network slices.
[015] Specifically, the first network node can obtain, from the terminal device, information about a network slice that is selected for the terminal device and that is used for access by the terminal device (or that the terminal device wants to access or is able to access), or can get,
Petition 870190077990, of 12/08/2019, p. 10/83
5/69 from the main network node, information about the network slice that the terminal device wants to access (or that the terminal device wants to access or is able to access).
[016] Optionally, if the third message is sent by the terminal device, the third message can be a radio resource control connection request (RRC Connection Request), a RRC Connection Reestablishment Request request or a complete RRC connection setup message (RRC Connection Setup Complete).
[017] Alternatively, if the third message is sent by the first main network node, the third message can be a message that requests to establish an interface between the first node of the access network and the first main network node, a configuration message of the initial terminal device context or other message used for communication between an access network node and a main network node. The first main network node can proactively send the third message to the first access network node, or it can send the third message to the first access network node based on a request message from the first access network node.
[018] In a possible implementation, the first message still includes at least one of the following: a network slice priority; a network slice identifier, a cell identity, a tracking area identifier or code, a paging area identifier, and a public land mobile network PLMN identifier that correspond to a network slice that is prohibited from being accessed by the device terminal; a network slice identifier, a cell identity, a tracking area identifier or code, a paging area identifier and a PLMN identifier that correspond to a network slice allowed to be accessed by the terminal device; a network slice reselection policy; and security information and service information that corresponds to at least one network slice in the first set of network slices, where the network slice reselection policy is used to indicate a way to select a network slice for the device terminal through a network node.
Petition 870190077990, of 12/08/2019, p. 11/83
6/69 [019] In a possible implementation, the first response message still includes at least one of the following: service information allowed to be established and / or service information not allowed to be established which is / is corresponding to at least a network slice in the second set of network slices.
[020] In a possible implementation, the second node in the network is the second node in the access network, and the method also includes: sending, through the first node in the network, a first request message to the second node in the network, where the first request message is used to request information about a network slice supported by the second network node, and the first request message includes information about a network slice supported by the first network node; and receiving, by the first network node, a first response request message sent by the second network node, where the first response request message includes information about the network slice supported by the second network node.
[021] Therefore, when the first network node and the second network node are both access network nodes, the first network node and the second network node can exchange information about a supported network slice with one another. For example, the first network node can send the first request message to the second network node, and the first request message can be used to request information about the network slice supported by the second network node. Optionally, the first request message can also include information about the network slice supported by the first network node. The second network node can respond with the first request for response message, and the first response request message can include information about the network slice supported by the second network node.
[022] Likewise, any two access network nodes in a communications system can exchange situations of the network slices supported by the two access network nodes in the previous mode. For example, an access network node currently accessed by the terminal device may, in the previous mode, obtain a situation of a network slice supported by an access network node to be accessed by the terminal device, in order to select a data slice. appropriate network for the terminal device based on the slice situation
Petition 870190077990, of 12/08/2019, p. 12/83
7/69 network supported by the access network node to be accessed.
[023] According to a second aspect, a method of communication is provided. The communication method includes: receiving, by a second network node, a first message sent by a first network node, where the first message includes a network slice identifier corresponding to at least one network slice in a first set of network slices, the network slice in the first set of network slices is a network slice that is selected for a terminal device and that is used for access by the terminal device, the first node in the network is a first node in the access network which is currently accessed by the terminal device, the second network node is a first main network node or a second access network node to be accessed by the terminal device, and the first main network node is a main network node of a communications system to which the first network node belongs; and sending, through the second network node, a first response message to the first network node, where the first response message includes a network slice identifier corresponding to at least one network slice in a second set of network slices ; the second set of network slices is a set of network slices that is used for access by the terminal device and which is determined by the second network node based on a situation of a network slice supported by the second access network node and the network slice identifier corresponding to at least one network slice in the first set of network slices, or the second set of network slices is a set of network slices that is used for access by the terminal device and which is determined by a second main network node based on a situation of a network slice supported by the second node of the access network and the network slice identifier corresponding to at least one network slice in the first set of network slices; and the second main network node is a main network node of a communications system to which the second access network node belongs.
[024] Therefore, according to the communication method in this modality of this request, the second network node can receive the first message sent by the first network node, where the first message includes the network slice identifier corresponding to at least one network slice in the first set of network slices. Based on the network slice identifier
Petition 870190077990, of 12/08/2019, p. 13/83
8/69 corresponding to at least one network slice in the first set of network slices included in the first message, the second network node can determine the network slice identifier corresponding to at least one network slice in the second set of network slices network. How the network slice identifier corresponding to at least one network slice in the second set of network slices is determined based on the situation of the network slice supported by the second node of the access network to be accessed by the terminal device, when the device terminal is delivered from the first node of the access network to the second node of the access network, the situation of the network slice supported by the second node of the access network can be considered, to determine a network slice that is supported by the second access network node and that must be accessed by the terminal device, thus ensuring a regular handover.
[025] Optionally, the first message can be a handover request message, or if the second node on the network is the second node on the access network, the first message can alternatively be another message used for communication between the first node of the access network and the second node of the access network, or if the second node of the network is the first main network node, the first message may alternatively be another message used for communication between the first node of the access network and the first main network node.
[026] Correspondingly, the first reply message may be a handover request confirmation message, or if the second node on the network is the second node on the access network, the first reply message may alternatively be another message used for communication between the first node of the access network and the second node of the access network, or if the second node of the network is the first main network node, the first reply message may alternatively be another message used for communication between the first node in the access network and the first main network node.
[027] In a possible implementation, the second set of network slices is determined by the first main network node or the second main network node, the first response message still includes a first non-access layer NAS message, the first NAS message
Petition 870190077990, of 12/08/2019, p. 14/83
9/69 includes the network slice identifier corresponding to at least one network slice in the second set of network slices, the first NAS message is used to instruct the terminal device to initiate a network slice reselection process, and the first reply message including the first NAS message is used to send the NAS message to the terminal device through the first node on the network.
[028] Optionally, the second set of network slices can be determined by the main network node in the communications system to which the first network node belongs, that is, the first main network node. In this case, the first node of the access network and the second node of the access network belong to the same communications system. Alternatively, the second set of network slices can be determined by the main network node in the communications system to which the second access network node belongs, that is, the second main network node. When the first response message is determined by a main network node (the first main network node or the second main network node), the first response message can also include the first NAS message, where the first NAS message includes the network slice identifier corresponding to at least one network slice in the second set of network slices determined by the main network node. After receiving the first reply message including the first NAS message, the first network node can transmit the first NAS message to the terminal device, so that the terminal device can start the network slice reselection process after receive the first NAS message.
[029] In a possible implementation, the second node in the network is the second node in the access network, the first main network node and the second main network node are the same main network node, and the method also includes: send , by the second network node, a fourth message for the first main network node, where the fourth message includes the network slice identifier corresponding to at least one network slice in the first set of network slices; and receiving, by the second network node, a fourth response message sent by the first main network node, where the fourth response message includes the first NAS message and the network slice identifier corresponding to at least one network slice in the second set of slices
Petition 870190077990, of 12/08/2019, p. 15/83
10/69 network, the first NAS message includes the network slice identifier corresponding to at least one network slice in the second set of network slices and the first NAS message is used to instruct the terminal device to initiate a process network slice reselection.
[030] In other words, if the second node on the network receiving the first message is the second node on the access network, after receiving the first message sent by the first node on the access network, the second node on the access network can determine, based on the network slice identifier corresponding to at least one network slice in the first set of network slices included in the first message, the network slice identifier corresponding to at least one network slice in the second set of network slices network. Alternatively, the second access network node can request a main network node in the communications system to which the second access network node belongs, that is, the first main network node, to determine the corresponding network slice identifier. at least one network slice in the second set of network slices.
[031] In a possible implementation, the method also includes: receiving, by the second node of the network, a fifth message sent by the terminal device, where the fifth message includes a second NAS message, the second NAS message includes the slice identifier of network corresponding to at least one network slice in the second set of network slices, and the second NAS message is used to indicate that the terminal device has updated the stored network slice information to the corresponding network slice identifier one network slice in the second set of network slices; and sending, by the second network node, a sixth message to the second main network node, where the sixth message includes the second NAS message.
[032] The second NAS message is generated based on the first NAS message, and after receiving the second NAS message, the second network node can send the second NAS message to a corresponding main network node.
[033] In a possible implementation, the first message still includes at least one of the following: a network slice priority; a network slice identifier, a cell identity, an identifier or
Petition 870190077990, of 12/08/2019, p. 16/83
11/69 tracking area code, a paging area identifier and a public land mobile network PLMN identifier that correspond to a network slice prohibited from being accessed by the terminal device; a network slice identifier, a cell identity, a tracking area identifier or code, a paging area identifier and a PLMN identifier that correspond to a network slice allowed to be accessed by the terminal device; a network slice reselection policy; and security information and service information that corresponds to at least one network slice in the first set of network slices, where the network slice reselection policy is used to indicate a way to select a network slice for the device terminal by a network node.
[034] In a possible implementation, the first response message still includes at least one of the following: service information allowed to be established and / or service information not allowed to be established that is / is corresponding to at least a slice of network in the second set of network slices.
[035] In a possible implementation, the first main network node and the second main network node are different main network nodes, the second network node is the first main network node, and the method also includes: send, at least second network node, a seventh message to the second main network node, where the seventh message includes the network slice identifier corresponding to at least one network slice in the first set of network slices; and receiving, by the second network node, a seventh response message sent by the second main network node, where the seventh response message includes the network slice identifier corresponding to at least one network slice in the second set of network slices .
[036] In other words, if the second network node that receives the first message sent by the first network node is the first main network node, the first main network node can determine directly, based on the network slice identifier corresponding to at least one network slice in the first set of network slices included in the first message, the network slice identifier corresponding to at least one network slice in the second set of network slices. Alternatively, if the first main network node and the second main network node are different main network nodes,
Petition 870190077990, of 12/08/2019, p. 17/83
12/69 the first main network node can request the second main network node to determine the network slice identifier corresponding to at least one network slice in the second set of network slices.
[037] In a possible implementation, if the second node in the network is the second node in the access network, the method may also include: receiving, by the second node in the network, a first request message sent by the first node in the network, where the first request message is used to request information about a network slice supported by the second network node, and the first request message includes information about a network slice supported by the first network node; and sending, by the second network node, a first response request message to the first network node, where the first response request message includes information about the network slice supported by the second network node.
[038] Therefore, when the first network node and the second network node are both access network nodes, the first network node and the second network node can exchange information about a supported network slice with each other. For example, the first network node can send the first request message to the second network node, and the first request message can be used to request information about the network slice supported by the second network node. Optionally, the first request message can also include information about the network slice supported by the first network node. The second network node can respond with the first request for response message, and the first response request message can include information about the network slice supported by the second network node.
[039] Likewise, any two nodes of the access network in a communications system can exchange the situations of network slices supported by the two nodes of the access network in the previous mode. For example, an access network node currently accessed by the terminal device may, in the previous mode, obtain a situation of a network slice supported by an access network node to be accessed by the terminal device, in order to select a data slice. appropriate network for the terminal device based on the situation of the network slice supported by the access network node to be accessed.
[040] According to a third aspect, a method of
Petition 870190077990, of 12/08/2019, p. 18/83
13/69 communication is provided. The communication method includes: sending, through a terminal device, a third message to a first network node, where the third message includes a network slice identifier corresponding to each network slice in a first set of network slices, each network slice in the first set of network slices is a network slice that is selected for the terminal device and that is used for access by the terminal device, and the first network node is a first access network node that is currently accessed by the terminal device; receive, by the terminal device, a second message sent by the first network node, where the second message includes a first non-access layer NAS message, the first NAS message includes a network slice identifier corresponding to each network slice in a second set of network slices, and the second set of network slices is a set of network slices that is used for access by the terminal device and that is determined by a second network node based on a one slice situation network supported by a second access network node and a network slice identifier corresponding to at least one network slice in the first set of network slices, or the second set of network slices is a set of network slices that is used for access by the terminal device and is determined by a second main network node based on a situation of a network slice supported by a second access network node and the identif network slice maker corresponding to at least one network slice in the first set of network slices, and the second main network node is a main network node of a communications system to which the second access network node belongs.
[041] In a possible implementation, the method also includes: sending, by the terminal device, a fifth message to the second node of the access network, where the fifth message includes a second NAS message, the second NAS message includes the identifier of network slice corresponding to each network slice in the second set of network slices, and the second NAS message is used to indicate that the terminal device has updated the stored network slice information to the corresponding network slice identifier for each network slice in the second set of network slices.
[042] According to a fourth aspect, a method of communication
Petition 870190077990, of 12/08/2019, p. 19/83
14/69 is provided. The communication method includes: sending, through a terminal device, a third message to a first network node, where the third message includes a network slice identifier corresponding to each network slice in a first set of network slices, each network slice in the first set of network slices is a network slice that is selected for the terminal device and that is used for access by the terminal device, and the first network node is a first node in the access network currently accessed by terminal device; and receiving, by the terminal device, a second message sent by the first network node, where the second message includes at least one of the following: redirection cell information and a network slice identifier corresponding to a network slice that is in the first set of network slices and for which the connection establishment is rejected. The redirect cell information indicates information about a cell that is selected by the first node in the network for the terminal device and that must be re-accessed by the terminal device.
[043] According to a fifth aspect, a communications device is provided, and is configured to execute the method, according to the first aspect and any possible implementation of the first aspect, or the method, according to the second aspect and any possible implementation of the second aspect, or the method, according to the third aspect and any possible implementation of the third aspect, or the method, according to the fourth aspect and any possible implementation of the fourth aspect. Specifically, the communications apparatus may include a unit configured to implement the method, according to the first aspect and any possible implementation of the first aspect, or a unit configured to implement the method, according to the second aspect and any possible implementation of the second aspect, or a unit configured to implement the method, according to the third aspect and any possible implementation of the third aspect, or a unit configured to implement the method, according to the fourth aspect and any possible implementation of the fourth aspect.
[044] According to a sixth aspect, a communications device is provided, and includes a memory and a processor. The memory is configured to store a computer program. The processor is
Petition 870190077990, of 12/08/2019, p. 20/83
15/69 configured to invoke the computer program in memory and conduct the computer program, so that the communications device executes the method, according to the first aspect and any possible implementation of the first aspect, or the method, according to with the second aspect and any possible implementation of the second aspect, or the method, according to the third aspect and any possible implementation of the third aspect, or the method, according to the fourth aspect and any possible implementation of the fourth aspect.
[045] According to a seventh aspect, a computer program product is provided, and the computer program product includes the computer program code. When the computer program code is executed by a communications unit, a processing unit, a transceiver or a processor of a communications device (for example, a network device or a terminal device), the communications device performs the methods, according to the first to the fourth aspects, or any possible implementation of the first to the fourth aspects.
[046] According to an eighth aspect, a computer-readable storage medium is provided. The computer-readable storage media stores a program and the program causes the user equipment to execute the methods, according to the first to fourth aspects, or any possible implementation from the first to the fourth aspects.
BRIEF DESCRIPTION OF THE DRAWINGS [047] Figure 1 is a schematic diagram of a wireless communications system, according to one embodiment of this application;
[048] Figure 2 is a schematic diagram of the interaction of a communication method, according to one modality of this request;
[049] Figure 3 is a schematic diagram of the interaction of a communication method, according to another modality of this request;
[050] Figure 4 is a schematic diagram of the interaction of a communication method, according to yet another modality of this request;
[051] Figure 5 is a schematic diagram of the interaction of a communication method, according to yet another modality of this request;
[052] Figure 6 is a schematic diagram of the interaction of a
Petition 870190077990, of 12/08/2019, p. 21/83
16/69 method of communication, in accordance with yet another modality of this request;
[053] Figure 7 is a schematic block diagram of a communications device, according to one embodiment of this request; and [054] Figure 8 is a schematic block diagram of a communications device, according to one embodiment of this application.
DESCRIPTION OF THE MODALITIES [055] The following describes the technical solutions of this application with reference to the attached drawings.
[056] Terminologies such as "component", "module" and "system" used in this specification are used to indicate entities related to computers, hardware, firmware, combinations of hardware and software, software or software being executed. For example, a component can be, but is not limited to, a process that runs on a processor, a processor, an object, an executable file, an execution thread, a program and / or a computer. As shown in the figures, both a computing device and an application that runs on a computing device can be components. One or more components can reside in a process and / or an execution thread, and a component can be located on one computer and / or distributed between two or more computers. In addition, these components can be run from various computer-readable media that store various data structures. For example, components can communicate using a local and / or remote process and according to, for example, a signal containing one or more data packets (for example, data from one component interacting with another component on a local system, a distributed system and / or over a network such as the Internet interacting with other systems using the signal).
[057] It should be understood that the modalities of this request can be applied to various communications systems that support a network slicing architecture, for example, a global system for a mobile communications system (Global System for Mobile Communications, GSM), a code division multiple access system (Code Division Multiple Access, CDMA), a broadband code division multiple access system (Wideband Code Division Multiple Access, WCDMA), a service system
Petition 870190077990, of 12/08/2019, p. 22/83
17/69 general packet radio (General Packet Radio Service, GPRS), a long term evolution system (Long Term Evolution, LTE), an advanced long term evolution system (Advanced Long Term Evolution, LTE-A) , a universal mobile telecommunications system (Universal Mobile Telecommunications System, UMTS), or a next generation communications system, for example, a new radio system (New Radio, NR) and an evolved LTE system (evolved LTE, eLTE) .
[058] Figure 1 shows a wireless communication system 100 to which a modality of this request applies. Wireless communications system 100 may include a network device 110. Network device 110 may be a radio access network device (Radio Access Network, RAN) or a primary network device (Core Network, CN) that communicates with a mobile device. The RAN device can be an access point (ACCESS POINT, AP) in a WLAN, a transceiver base station (Base Transceiver Station, BTS) in GSM or CDMA, a B node (NodeB, NB) in WCDMA, a B node evolved (Evolved Node B, eNB or eNodeB) in LTE, a relay node, an access point, a device in the vehicle, a wearable device, a network device on a future 5G network, or a network device on a future evolved PLMN network, for example, a base station that can be connected to a main 5G network device, a Transmission and Reception Point (TRP), a centralized unit (Centralized Unit, CU) or a unit distributed (Distributed Unite, DU). CN CN device can be a mobility management entity (Mobility Manegement Entity, MME) or a gateway (Gateway) in LTE, and it can also be a control plane (Control Plane, CP), network function (Network Function, NF ) and a user plane network function (User Plane, UP) on a 5G network, for example, a common CP NF (Common CP NF, CCNF), session management NF (Session Management NF, SMF) or similar .
[059] The communications system in this mode of this application supports a network slicing architecture, and network slices in the communications system can share a network device and / or a network resource, or can exclusively occupy a network device and / or a network resource. For example, a network slice A (NS A for short) and a network slice B (NS B for short) shown in Figure 1 can share a RAN
Petition 870190077990, of 12/08/2019, p. 23/83
18/69 and a CCNFs, and a C network slice (NS C for short) can exclusively occupy a RAN network device and does not share a CN device with another network slice.
[060] In addition, in this embodiment of this request, a network device provides a service to a cell, and a terminal device communicates with the network device through the use of a transmission resource (for example, a domain resource frequency or a spectrum resource) used by the cell. The cell can be a corresponding cell for the network device (for example, a base station), and the cell can be a macro base station, a hyper cell, or it can be a base station corresponding to a small cell (small cell). The small cell in this report may include: a metrocell (Metro Cell), a microcell (Micro Cell), a pico cell (Pico Cell), a femto cell (Femto Cell) and the like. These small cells have low coverage and low transmission power characteristics and are applicable to high-rate data transmission services.
[061] Wireless communication system 100 still includes at least one terminal device 120 located within the coverage of network device 110. The terminal device can also be referred to as user equipment (User Equipment, UE), an access terminal , a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communications device, a user agent or a wireless device user. The terminal device can be a station (STATION, ST) on a Wireless Local Area Network, WLAN, a cell phone, a cordless phone, a Session Initiation Protocol phone , SIP), a wireless remote access station (Wireless Local Loop, WLL), a personal digital assistant (Personal Digital Assistant, PDA), a portable device having a wireless communication function, a relay device, a computing, another processing device connected to a wireless modem, a device in the vehicle, a wearable device, a terminal device in a next generation communications system, for example, a fifth generation network (fifth generation, 5G), a terminal device on a future terrestrial mobile network
Petition 870190077990, of 12/08/2019, p. 24/83
19/69 evolved public (Public Land Mobile Network, PLMN) or similar.
[062] As an example, instead of a limitation, in this modality of this application, the terminal device can also be a wearable device. A wearable device can also be referred to as a wearable smart device, and is a generic name for devices that can be used and that are developed with the application of a technology used to carry out smart designs for daily use, such as glasses, gloves, a watch. , clothes or shoes. A wearable device is a portable device that is worn directly on a human body or integrated with a user's clothing or accessory. The wearable device is not just a hardware device and implements powerful functions through software support, data exchange and cloud-based interaction. In a broad sense, portable smart devices have a full range of functions and a large size, and do not rely on smartphones to implement all or some functions, for example, smart watches and smart glasses; or wearable smart devices only focus on one type of application function and need to work with other devices, such as smartphones, for example, various smart bands and smart jewelry for monitoring body signals.
[063] A communication method and a communication device provided in these modalities of this application can be applied to a network device. The network device can include an access network device and a primary network device, and the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware, such as a central processing unit (Central Processing Unit, CPU), a memory management unit (Memory Management Unit, MMU) and a memory (also referred to as a main memory). The operating system can be any one or more types of computer operating systems that implement service processing through the use of a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system or a Windows operating system. The application layer includes applications such as a browser, an address book,
Petition 870190077990, of 12/08/2019, p. 25/83
20/69 word processing or instant messaging software. Furthermore, in the modalities of this request, a specific structure of a body of execution of the communication method is not particularly limited in these modalities of this request, as long as the communication can be implemented using a program that executes the code that writes the communication method in these modalities of this application and based on the method of communication in these modalities of this application. For example, the body of execution of the communication method in these modalities of this application can be a network device or a functional module in the network device that can invoke the program and execute the program.
[064] In addition, aspects or characteristics of these modalities of this application can be implemented as a method, a device or a product that uses standard programming and / or engineering technologies. The term "product" used in this application encompasses a computer program that can be accessed from any component, carrier or computer-readable media. For example, computer-readable media may include, but is not limited to: a magnetic storage component (for example, a hard disk, a floppy disk, or a magnetic tape), an optical disk (for example, a compact disk (Compact Disc, CD), a versatile digital disc (Digital Versatile Disc, DVD)), a smart card and an instant memory component (for example, an erasable Programmable Read-Only Memory, EPROM), card, baton or key drive). In addition, the various storage media described in this specification can indicate one or more devices and / or other machine-readable media that are used to store information. The term "machine-readable media" can include but is not limited to a radio channel and several other media can store, contain and / or transport an instruction and / or data.
[065] The following describes in detail the method of communication in the modalities of this application with reference to Figure 2 to Figure 6.
[066] It should be understood that Figure 2 to Figure 6 are schematic flowcharts of the communication method in the modalities of this application, and show detailed communication steps or operations of the method. However, these steps or operations are merely examples. In these
Petition 870190077990, of 12/08/2019, p. 26/83
21/69 modalities of this order, other operations or variations of the operations in Figure 2 to Figure 6 can alternatively be performed. In addition, each step in Figure 2 for Figure 6 can be performed, according to a different sequence from that shown in Figure 2 for Figure 6, and possibly not all operations in Figure 2 for Figure 6 need to be performed.
[067] Figure 2 is a schematic diagram of the interaction of a communication method 200, according to one modality of this request. Communication method 200 is described from an equipment interaction perspective. Method 200 can be applied to the communication system 100 shown in Figure 1.
[068] As shown in Figure 2, in 201, a first network node can send a first message to a second network node.
[069] In 202, the first network node receives a first response message sent by the second network node.
[070] The first node in the network is a first node in the access network (hereinafter referred to as a “RAN1 node”) which is currently accessed by a terminal device, and the second node in the network can be a first node main network, where the first main network node (hereinafter referred to as a “CN1 node”) is a main network node in a communications system to which the RAN1 node belongs; or the second node of the network can be a second node of the access network (hereinafter referred to as a “RAN2”) to be accessed by the terminal device.
[071] In addition, the first message includes a network slice identifier corresponding to at least one network slice in a first set of network slices (for ease of distinction and description, denoted as an NS Set1). Each network slice corresponds to a network slice identifier. The first message can include the network slice identifiers corresponding to some or all of the network slices in the first set of network slices. At least one network slice in the first set of network slices in the first message can also be considered as a set (for ease of description and interpretation, denoted as an NS Set1RAN1). Specifically, NS Set1-RAN1 is a subset of NS Set1, and NS Set1 -RAN1 can include some or all of the network slices in NS Set1.
Petition 870190077990, of 12/08/2019, p. 27/83
22/69 [072] The first reply message includes a network slice identifier corresponding to at least one network slice in a second set of network slices (for ease of distinction and description, denoted as an NS Set2). The second set of network slices can be a network slice that is determined by the second network node and that is used for access by the terminal device. Alternatively, the second set of network slices includes a network slice that is determined by a second main network node (hereinafter referred to as a “CN2 node”) and which is used for access by the terminal device. The CN2 node is a major network node in a communications system to which RAN2 belongs. In other words, the second set of network slices can be determined by RAN2, can be determined by CN1, or can be determined by CN2. When RAN1 and RAN2 belong to the same communication system, CN1 and CN2 are the same main network node.
[073] Particularly, for ease of description and interpretation, when the second set of network slices is determined by RAN2, NS Set2 is denoted as an NS Set2-RAN2; when the second set of network slices is determined by CN1, NS Set2 is denoted as NS Set2-CN1; and when the second set of network slices is determined by CN2, NS Set2 is denoted as NS Set2-CN2.
[074] Optionally, the RAN1 node and the RAN2 node can be network devices in the wireless communications system shown in Figure 1, for example, a base station in a 5G system, a base station in an eLTE system , or a base station on an LTE system that can be connected to a main 5G network. The CN1 node and the CN2 node can be main network devices in the 5G system or main network devices in the eLTE system. The terminal device can be the terminal device in the wireless communications system shown in Figure 1.
[075] Specifically, the network slices that the terminal device wants to access (or, selects to access or is able to access) form the first set of network slices, that is, NS Set1. Each network slice in NS Set1 corresponds to a network slice identifier. The network slice identifier for each network slice can be represented using at least one of the following parameters:
Petition 870190077990, of 12/08/2019, p. 28/83
23/69
1. Network slice type information: for example, network slice type information may indicate a type of network slice such as an Enhanced Mobile BroadBand (eMBB) service, ultra-reliable communications and low latency (Ultra-Reliable Low Latency Communications, URLLC) and massive machine type communications (Massive Machine Type Communication, mMTC). Optionally, network slice type information can also indicate an end-to-end network slice type, including a RAN to CN network slice type, a RAN side network slice type, or a slice type network on the CN side;
2. Type of service information: related to a specific service; for example, service type information may indicate a service feature of a video service, a Vehicle Internet service, a voice service and the like, or information about a specific service;
3. Tenant Information (Tenant): used to indicate information about a customer that creates or leases a network slice, for example, Tencent or the Grid State;
4. User group information: used to indicate a user's grouping group information based on a characteristic, for example, a user level;
5. Slice group information: used to indicate a network slice group that is formed based on a characteristic, for example, all network slices can be accessed by the terminal device that is used as a slice group or a network slice group is classified according to another standard;
6. Network slice instance information: used to indicate an instance identifier and characteristic information that is created for the network slice. For example, an identifier can be distributed to a network slice instance, and is used to indicate the network slice instance; alternatively, a new identifier can be mapped based on the network slice instance identifier, to associate the network slice instance, so that a receiver can identify, based on the identifier, a specific network slice instance indicated by the identifier; and
7. Dedicated Core Network identifier,
Petition 870190077990, of 12/08/2019, p. 29/83
24/69
DCN): the identifier is used to uniquely indicate a dedicated main network in the LTE system or in the eLTE system, for example, a dedicated main network in the Internet of Things. Optionally, the mapping can be performed on the DCN identifier and a network slice identifier, so that the network slice identifier can be obtained through mapping based on the DCN identifier, or the DCN identifier can be obtained through mapping with based on the network slice identifier.
[076] It should be understood that in this modality of this request, for each network slice in the first set of network slices or the second set of network slices, at least one of the previous parameters can be used to represent a network slice identifier corresponding to each network slice. For example, the network slice identifier for each network slice can be represented using a type of network slice, it can be represented using a type of network slice and a type of service, or it can be represented using a type of service together with tenant information. This is not limited to this type of order. The details on how to represent a network slice identifier corresponding to a network slice are not described below again.
[077] Optionally, a specific form of encoding the network slice identifier corresponding to at least one network slice in the first set of network slices included in the first message is not limited. The network slice identifier corresponding to at least one network slice can be carried in different fields of the first message to represent different network slice identifiers, or the network slice identifier corresponding to at least one network slice can be replaced. through the use of an abstracted index value, where different index values correspond to different network slices.
[078] Optionally, the first message can be a handover request message. Alternatively, if the second node on the network is the RAN2 node, the first message can be another message used for communication between the RAN1 node and the RAN2 node. Alternatively, if the second node on the network is the CN1 node, the first message can be a handover required message, or it can be another message used for communication between the RAN1 node and the CN1 node.
Petition 870190077990, of 12/08/2019, p. 30/83
25/69 [079] Correspondingly, the first response message can be a handover request acknowledgment message. Alternatively, if the second node on the network is the RAN2 node, the first response message can be another message used for communication between the RAN1 node and the RAN2 node. Alternatively, if the second node on the network is the CN1 node, the first response message may be a handover command message, or it may be another message used for communication between the RAN1 node and the CN1 node. .
[080] Optionally, in a modality, before 201, method 200 may also include 210. In 210, the first network node receives a third message sent by the terminal device or the first main network node. The third message includes the network slice identifier corresponding to each network slice in the first set of network slices.
[081] In other words, the first set of network slices includes network slices that the terminal device needs to access, the third message can include network slice identifiers corresponding to the network slices in the first set of network slices, and the The RAN1 node can determine, based on the third message, the network slice identifiers corresponding to the network slices in the first set of network slices. The third message can be sent by the terminal device, or sent by the first main network node. Specifically, the network slice identifiers corresponding to the network slices in the first set of network slices can be notified to the RAN1 node by the terminal device, or they can be notified to the RAN1 node by the first main network node, that is, the CN1 node.
[082] Specifically, if the third message is sent by the terminal device, the third message can be a radio resource control connection request ((Radio Resource Control, RRC) Connection Request), a RRC connection reestablishment request ( RRC Connection Reestablishment Request) or a RRC Connection Setup Complete message, where the RRC connection request is used to request the establishment of a connection to the network device, the RRC connection reestablishment request is used to request the reestablishment of a connection to the network device, and
Petition 870190077990, of 12/08/2019, p. 31/83
26/69 the full RRC connection setup message is used to indicate that the connection to the network device is complete.
[083] Alternatively, if the third message is sent by the CN1 node, the third message can be a message that requests to establish an interface between the RAN1 node and the CN1 node, an initial context configuration message from the UE, or another message used for communication between a RAN node and a CN node. The CN1 node can proactively send the third message to the RAN1 node, or it can send the third message to the RAN1 node based on a request message from the RAN1 node.
[084] Figure 3 is a schematic diagram of the interaction of a communication method, according to another modality of this request. In a mode shown in Figure 3, a RAN1 node can obtain, from a CN1 node, information about a network slice that a terminal device needs to access (either select to access or is required to access).
[085] As shown in Figure 3, method 300 can include the following steps.
[086] At 301, the CN1 node can send a first network slice management request message to the RAN1 node. Optionally, the first network slice management request message can be used for context management, service management, load management and the like of the end device. The first network slice management request message can be an initial UE configuration message, a bearer establishment request, or other message used for communication between a RAN node and a CN node. This is not limited to this type of order.
[087] Optionally, the first network slice management request message can include at least one of the following:
1. A corresponding identifier for the terminal device: The corresponding identifier for the terminal device can be identifying information that can uniquely identify the terminal device, such as an international mobile subscriber identity (IMSI), a temporary mobile subscriber identity
Petition 870190077990, of 12/08/2019, p. 32/83
27/69 (Temporary Mobile Subscriber Identification Number, TMSI), or a random number;
2. A frequency priority and an access technology priority that correspond to at least one network slice in a first set of network slices: used for terminal mobility management; for example, the terminal can determine a priority for cell selection or reselection based on frequency priority, to select a target cell with a high frequency priority;
3. A priority corresponding to at least one network slice in the first set of network slices: used for mobility management, admission control and the like of the terminal device; for example, the terminal device may consider supporting a high priority cell in cell selection or cell reselection when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source-side RAN node can preferably consider supporting a neighboring RAN node in a high priority network slice as a RAN node on the target side for handover, and the RAN node of the the target side can still preferably admit a service carrier corresponding to the high priority network slice;
4. Configuration information related to a closed subscriber group (Closed Subscriber Group) corresponding to at least one network slice in the first set of network slices: for example, a CSG member situation, used to indicate whether the terminal is a CSG member;
5. Track (trace) information corresponding to at least one network slice in the first set of network slices: used for device commissioning, for example, start of tracking, end of tracking and cell service tracking;
6. A Minimization of Drive Tests (MDT) parameter corresponding to at least one network slice in the first set of network slices: for example, if minimizing unit tests is allowed, a list of public land mobile networks (Public Land Mobile Network, PLMN), cells and tracking areas that allow the minimization of unit tests;
7. Service information corresponding to at least one network slice in the first set of network slices: for example, information about
Petition 870190077990, of 12/08/2019, p. 33/83
28/69 establishment, modification and release related to the carrier, related to the session and related to the flow;
8. Load information corresponding to at least one network slice in the first set of network slices: for example, downtime indication information used to instruct the RAN node to perform load control, or load indication information end of overload used to indicate the end of load control of the network slice;
9. A network slice identifier corresponding to a network slice prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate at least one network slice that is prohibited from being accessed or allowed to be accessed by the terminal device;
10. A cell identity corresponding to a network slice prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate at least one cell corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device. Optionally, the cell identity corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be stored based on a network slice priority, and can be used for managing the mobility of the terminal device. For example, the terminal device can preferably select or reselect a high priority cell when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source side RAN network element may preferably consider supporting a neighboring RAN network element in which the high priority cell is located as a RAN network element on the target side;
11. An identifier or tracking area code corresponding to a network slice that is prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate at least one tracking area that is prohibited from being accessed or allowed to be accessed by the terminal device . Optionally, a tracking area identifier or code in the tracking area identifier or code corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be stored based on a network slice priority, and can be used for device mobility management
Petition 870190077990, of 12/08/2019, p. 34/83
29/69 terminal. For example, the terminal device can preferably select or reselect a cell in which a high priority tracking area is located when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source-side RAN network element can preferably consider a neighboring RAN network element in which the high priority area is located as a RAN network element on the target side;
12. A paging area identifier corresponding to the slice of the network prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate at least one paging area of a main network and / or access network prohibited from being accessed or allowed to be accessed by the terminal device. Optionally, the paging area identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be stored based on a network slice priority and can be used for managing the mobility of the terminal device. For example, the terminal device may preferably select or reselect a cell in which a high priority paging area is located when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source-side RAN network element may preferably consider supporting a neighboring RAN network element in which the high priority paging area is located as a RAN network element on the target side;
13. A public land mobile network identifier (Public Land Mobile Network, PLMN) corresponding to a network slice prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate an identifier of a PLMN that currently serves the terminal device , and / or a list of equivalent PLMN identifiers allowed to be accessed by the terminal device. Optionally, the PLMN identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be stored based on a network slice priority, and can be used for managing the mobility of the terminal device. For example, the terminal device can preferably select or reselect a cell in which a high priority PLMN is
Petition 870190077990, of 12/08/2019, p. 35/83
30/69 located when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source-side RAN network element may preferably consider supporting a neighboring RAN network element in which the high priority PLMN is located as a RAN network element on the target side; and
14. A network slice reselection policy: The network slice reselection policy can indicate whether a network device is allowed to always select one or more network slices for the terminal device, or whether the network device can select another network slice for the terminal device in a handover or cell reselection mode. For example, for a network slice indicated by at least one network slice identifier, an identifier of at least one network slice that can replace the network slice may be included. Optionally, the identifier out of at least one network slice that can replace the network slice can be stored based on a priority. A criterion for determining a priority is not limited in this modality of this request. For example, sorting can be performed based on a network slice priority.
[088] With reference to the preceding descriptions, it can be learned that if a third message is sent by a first main network node, that is, the CN1 node, the CN1 node can send the third message to the RAN1 using step 301 shown in Figure 3, to notify the RAN1 node of information about the network slice that the terminal device wants to access. In this case, the third message can be the first network slice management request message at 301 shown in Figure 3.
[089] Therefore, if the third message is sent by the first main network node, that is, the CN1 node, the third message can be the first network slice management request message, so that in 201, the third message may also include at least a portion of the information included in the first network slice management request message described above, for example, the network slice identifier, cell identity, area code identifier or code tracking, the paging area identifier and the PLMN identifier that correspond to the network slice prohibited from being accessed by the terminal device; the network slice identifier, the cell identity, the identifier
Petition 870190077990, of 12/08/2019, p. 36/83
31/69 or tracking area code, the paging area identifier and the PLMN identifier that correspond to the network slice allowed to be accessed by the terminal device; the network slice reselection policy; and security information and service information that corresponds to at least one network slice in the first set of network slices.
[090] Optionally, as shown in Figure 3, at 302, the RAN1 node can still send a first network slice management request response message to the CN1 node, where the first network management request response message network slice may indicate that the RAN1 node accepts or rejects the first network slice management request message from the CN1 node. If the RAN1 node rejects the first network slice management request message from the CN1 node, the first network slice management request response message can still carry a cause of rejection, for example, the cause of rejection can be requests to manage some or all of the network slices in the first set of network slices that cannot be satisfied.
[091] As shown in Figure 3, at 303, the RAN1 node can still send a second network slice management request message to the CN1 node. Optionally, the second network slice management request message can be used to notify the CN1 node of information about a network slice currently supported by the RAN1 node. In this case, the second network slice management request message can include information about the network slice supported by the RAN1 node. For detailed content of the information, see the preceding descriptions. For brevity, the details are not described in this report again.
[092] Optionally, the second network slice management request message can also be used for context management, service management, load management, and the like of the terminal device. In this case, the second network slice management request message can include at least one of the following:
1. An RAN node identifier: the RAN node identifier is used to uniquely identify an RAN node globally;
Petition 870190077990, of 12/08/2019, p. 37/83
32/69
2. Cell information corresponding to at least one network slice in the first set of network slices: for example, a cell identity, a physical cell identity, frequency information, an identifier or tracking area code, an identifier paging area and physical access channel configuration information that is from a service cell, in which at least one network slice is located, from the RAN node, and a cell identity, a physical cell identity, information frequency, a tracking area identifier or code, a paging area identifier and physical access channel configuration information that is from a neighbor cell of each service cell;
3. A list of carriers to be released, a session list to be released, and a flow list to be released that correspond to at least one network slice in the first set of network slices: respectively used to indicate that the CN1 node needs to release a carrier, session or flow that are established by the terminal device;
4. A list of carriers to be modified, a session list to be modified and a flow list to be modified that correspond to at least one network slice in the first set of network slices: respectively used to indicate that the node CN1 needs to modify related service information of a carrier, session or flow that is established by the terminal device;
5. A context list of the terminal to be released corresponding to at least one network slice in the first set of network slices: used to request the CN1 node to release an interface that is established between the RAN1 node and the network node. CN1 and that is specific to the corresponding network slice; and
6. A context list of the terminal to be modified corresponding to at least one network slice in the first set of network slices: used to request the context information to be modified corresponding to the network slice from the CN1 node, for example example, information from closed subscriber group members (Closed Subscriber Group, CSG).
[093] Optionally, the second network slice management request message can be a message that requests to establish an interface between the RAN1 node and the CN1 node, a UE context release message, or another message used for communication between the
Petition 870190077990, of 12/08/2019, p. 38/83
33/69
RAN and the CN node. This is not limited to this type of order.
[094] Therefore, a RAN node in a communications system can send, in a manner described in 303, a second network slice management request to a CN node in the communications system to which the RAN node belongs, to notify the CN node of information about a network slice supported by the RAN node. In this way, the NC node can perform mobility management based on information about the network slice supported by the RAN node, for example, determining a network slice to be accessed for the terminal device based on information about the slice network supported by the RAN node.
[095] Sending the second network slice management request message just before sending a first message. In other words, 303 is performed just before 201. Alternatively, 303 can be performed before 201 for a period of time. For example, the RAN1 node can send the second network slice management request message to the CN1 at a specific time, to notify the CN1 node of a network slice situation supported by the RAN1 node, to facilitate the subsequent mobility management by the CN1 node. In this case, when RAN1 sends the first message to CN1, the CN1 node can determine the network slice to be accessed by the terminal device based on the situation of the network slice supported by the RAN1 node.
[096] Optionally, a RAN2 node can also send a network slice management request message corresponding to the CN1 node in the manner described in 303, to notify the CN1 node of a situation of a network slice supported by the node of RAN2. In other words, an access network node in the communications system can send, in the manner described in 303, a network slice management request message corresponding to a major network node in the communications system to which the network node access point belongs to, to notify the main network node of a situation of a network slice supported by the access network node, so that the main network node in the communications system can select an appropriate network slice for the terminal device based on a situation of a network slice supported by each access network node.
[097] Optionally, as shown in Figure 3, in 304, the node
Petition 870190077990, of 12/08/2019, p. 39/83
34/69 from CN1 can further send a second network slice management request response message to the RAN1 node, where the second network slice management request response message is used to indicate that the CN1 node successfully received the second network slice management request message sent by the RAN1 node.
[098] Optionally, in addition to the network slice identifier corresponding to each network slice in the first set of network slices, a first message can also include at least one of the following:
a network slice identifier, a cell identity, a tracking area identifier or code, a paging area identifier and a public land mobile network PLMN identifier that correspond to a network slice prohibited from being accessed by the device terminal; a network slice identifier, a cell identity, a tracking area identifier or code, a paging area identifier and a PLMN identifier that correspond to a network slice allowed to be accessed by the terminal device; a network slice reselection policy; and security information and service information that corresponds to at least one network slice in the first set of network slices, where the network slice reselection policy is used to indicate a way to select a network slice for the device terminal through a network node.
[099] Specifically, the network slice identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device is used to indicate at least one network slice that is prohibited from being accessed or allowed to be accessed by the terminal device . The cell identity corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device is used to indicate at least one cell corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device. The tracking area identifier or code corresponding to the network slice that is prohibited from being accessed or allowed to be accessed by the terminal device is used to indicate at least one tracking area that is prohibited from being accessed or allowed to be accessed by the terminal device. Optionally, a tracking area code or identifier in the tracking area code or identifier
Petition 870190077990, of 12/08/2019, p. 40/83
35/69 corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be stored based on a network slice priority, and can be used for managing the mobility of the terminal device. The paging area identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device is used to indicate at least one paging area of a main network and / or an access network corresponding to the prohibited network slice to be accessed or allowed to be accessed by the terminal device. Optionally, a paging area identifier in the paging area identifier that is prohibited from being accessed or allowed to be accessed by the terminal device can be stored based on a network slice priority and can be used for managing the mobility of the terminal device. The PLMN identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device is used to indicate an identifier of a PLMN currently serving the terminal device, and / or a list of equivalent PLMN identifiers allowed to be accessed by the terminal device. Optionally, the PLMN identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be stored based on a network slice priority and can be used for managing the mobility of the terminal device. The network slice reselection policy can indicate whether a network device is allowed to always select one or more network slices for the terminal device, or whether the network device can select another network slice for the terminal device in a mode cell handover or reselection. For example, for a network slice indicated by at least one network slice identifier, an identifier of at least one network slice that can replace the network slice may be included. Optionally, the identifier among at least one network slice that can replace the network slice can be classified based on a priority. A criterion for determining a priority is not limited in this modality of this request. For example, sorting can be performed based on a network slice priority. Security information corresponding to at least one network slice in the first set of network slices (that is, an NS Set1-RAN1) can include, for example,
Petition 870190077990, of 12/08/2019, p. 41/83
36/69 encryption location indication, where the encryption location indication information can indicate whether the encryption location is located on a RAN node or a CN node, or encryption key indication information, where the encryption information encryption key indication are used to notify RAN2 of an encryption key used by at least one network slice in the first set of network slices.
[0100] The network slice reselection policy can indicate whether a network device is allowed to always select one or more network slices for the terminal device, or whether the network device can select another network slice for the terminal device in a handover or cell reselection mode. For example, for a network slice indicated by at least one network slice identifier, an identifier of at least one network slice that can replace the network slice may be included. Optionally, the identifier among at least one network slice that can replace the network slice can be classified based on a priority. A criterion for determining a priority is not limited in this modality of this request. For example, sorting can be performed based on a network slice priority.
[0101] Service information corresponding to at least one network slice in the first set of network slices (that is, NS Set1-RAN1) can include at least one of the following:
1. Bearer information corresponding to a network slice that needs to be established or admitted in NS Set1 -RAN1: for example, a bearer identifier, a quality of service at bearer level (Qualityof-Service, QoS) parameter or a tunnel termination point;
2. Session information corresponding to a network slice that needs to be established or admitted to NS Set1-RAN1: for example, a session identifier, a session-level QoS parameter or a tunnel termination point; and
3. Flow information corresponding to the network slice that needs to be established or admitted to NS Set1-RAN1: for example, a flow identifier, a flow-level QoS parameter or a tunnel termination point.
[0102] Optionally, the first message can also include a
Petition 870190077990, of 12/08/2019, p. 42/83
37/69 frequency priority and access technology priority that correspond to at least one network slice in the first set of network slices, and frequency priority and access technology priority are used for terminal mobility management . For example, the terminal can determine a priority for cell selection or reselection based on frequency priority, to select a target cell with a high frequency priority.
[0103] Optionally, the first message can also include a priority corresponding to at least one network slice in the first set of network slices, and the priority is used for mobility management, admission control and the like of the terminal device. The terminal device may consider supporting a high priority cell in cell selection or cell reselection when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source-side RAN node may preferably consider supporting a neighboring RAN node on a high priority network slice as a RAN node on the target side for handover, and the RAN node on the The target side can preferably still admit a service carrier corresponding to the high priority network slice.
[0104] Optionally, the first message may also include context information from the terminal device, for example, a network slice identifier corresponding to at least one network slice signed by the terminal device.
[0105] Optionally, the first message can also include a handover cause, where the handover cause is used to indicate a cause for the terminal device to be delivered from the RAN1 node to the RAN2 node. For example, the handover cause may be a cause in a wireless network layer (for example, the handover is triggered due to signal quality or resource-based optimization).
[0106] Optionally, the first message may also include a temporary identifier corresponding to the terminal device, and the temporary identifier is used to search for stored context information of the terminal device via a main network element.
[0107] Optionally, the first message may also include a main network control function entity identifier associated with
Petition 870190077990, of 12/08/2019, p. 43/83
38/69 the terminal device.
[0108] With reference to Figure 2, the following describes in detail how to determine a network slice identifier corresponding to at least one network slice in a second set of network slices in different modalities.
[0109] Mode 1: a second network node is a RAN2 node, and a second set of network slices is determined by the RAN2 node and denoted as an NS Set2-RAN2.
[0110] In this case, in 201, a RAN1 node sends a first message to the RAN2 node.
[0111] In 202, the RAN1 node receives a first reply message sent by the RAN2 node.
[0112] The first message includes a network slice identifier corresponding to at least one network slice in a first set of network slices, and the first response message includes the network slice identifier corresponding to at least one network slice. network in the second set of network slices.
[0113] Specifically, the second node in the network that receives the first message sent by the RAN1 node is the RAN2 node. Based on the network slice identifier corresponding to at least one network slice in the first set of network slices (that is, an NS Set1-RAN1) included in the first message, the RAN2 node can directly determine the second set of slices network, ie NS Set2-RAN2, with reference to a situation of a network slice supported by the RAN2 node.
[0114] Optionally, NS Set2-RAN2 can include some or all network slices in NS Set1-RAN1. In other words, NS Set2-RAN2 is a subset of NS Set1-RAN1. A network slice that is determined by the RAN2 node and that is used for access by a terminal device can include some or all of the network slices in network slices that the terminal device wants to access (either it needs access or needs access). The RAN2 node can filter some network slices based on the situation of the network slice supported by the RAN2 node.
[0115] Optionally, the RAN2 node can alternatively reselect some or all network slices for the terminal device. In
Petition 870190077990, of 12/08/2019, p. 44/83
39/69 In other words, NS Set2-RAN2 may not be a subset of NS Set1RAN1. NS Set2-RAN2 can also include a network slice that is not included in NS Set1-RAN1. The network slice that is included in NS Set2-RAN2 but not included in NS Set1-RAN1 can be a network slice that is reselected to the terminal device by RAN2. Alternatively, RAN2 can update information about some or all of the network slices on NS Set1-RAN1.
[0116] Optionally, the first reply message includes the network slice identifier corresponding to at least one network slice in the second set of network slices. In other words, the first reply message can include network slice identifiers corresponding to some or all of the network slices in NS Set2-RAN2.
[0117] Optionally, in addition to the network slice identifier corresponding to at least one network slice in the second set of network slices (ie NS Set2-RAN2), the first reply message can also include at least one among the following:
service information allowed to be established and service information not allowed to be established that corresponds to at least one network slice in the second set of network slices.
[0118] Specifically, each network slice corresponds to the corresponding service information, such as carrier information, session information or flow information. RAN2 can only be allowed to establish service information corresponding to some network slices, it can be allowed only to establish some service information corresponding to some network nodes, or it is likely that service information corresponding to a network slice does not can be established. In this case, the first reply message may include service information allowed to be established and / or service information not allowed to be established which is / is corresponding to at least one network slice in NS Set2-RAN2.
[0119] Optionally, in Mode 1, the first message can be a handover request message, or it can be another message used for communication between a RAN node and another RAN node.
Petition 870190077990, of 12/08/2019, p. 45/83
40/69
Correspondingly, the first response message can be a handover request confirmation message, or it can be another message used for communication between the RAN node and the other RAN node.
[0120] Optionally, the RAN1 node and the RAN2 node can also obtain, in advance, information about a network slice supported by each other. Figure 4 is a schematic diagram of the interaction of a communication method 400, according to yet another modality of this application. In a mode shown in Figure 4, the RAN1 node and the RAN2 node can still obtain, in advance, information about the network slice supported by each other. As shown in Figure 4, at 401, the RAN1 node can send a first request message to the RAN2 node, where the first request message is used to exchange application-side configuration information between the two RAN nodes. For example, the first request message may include the following information:
1. A RAN1 node identifier: the RAN1 node identifier is used to uniquely identify the RAN1 node globally;
2. Information about a service cell of the RAN1 node and a corresponding neighbor cell for each service cell: for example, cell identities, physical cell identities, frequency information, tracking area codes or identifiers and area identifiers paging that correspond to the service cell and the corresponding neighbor cell for each service cell; a network slice identifier, physical access channel configuration or network slice mobility parameter information that corresponds to a supported network slice, for example, a handover triggered change parameter, where the triggered change parameter by handover is used to indicate a limit to start preparing for handover from one cell to another cell;
3. A network slice identifier corresponding to a network slice that is prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate at least one network slice that is prohibited from being accessed or allowed to be accessed by the terminal device;
4. A cell identity corresponding to a network slice prohibited from being accessed or allowed to be accessed by the terminal device:
Petition 870190077990, of 12/08/2019, p. 46/83
41/69 used to indicate at least one cell corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device. Optionally, the cell identity corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be configured based on a network slice priority, and can be used for managing mobility of the terminal device. For example, the terminal device can preferably select or reselect a high priority cell when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source side RAN network element may preferably consider supporting a neighboring RAN network element in which the high priority cell is located as a RAN network element on the target side;
5. An identifier or tracking area code corresponding to the network slice that is prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate at least one tracking area that is prohibited from being accessed or allowed to be accessed by the terminal device. Optionally, an identifier or tracking area code in the identifier or tracking area code corresponding to the network slice that is prohibited from being accessed or allowed to be accessed by the terminal device can be configured based on a network slice priority, and can be used for UE mobility management. For example, the terminal device can preferably select or reselect a cell in which a high priority tracking area is located when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source side RAN network element can preferably consider supporting a neighboring RAN network element in which the high priority tracking area is located as a RAN network element on the target side;
6. A paging area identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate at least one paging area of a main network and / or access network corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device. Optionally, a paging area identifier corresponding to the prohibited network slice
Petition 870190077990, of 12/08/2019, p. 47/83
42/69 to be accessed or allowed to be accessed by the terminal device can be configured based on a network slice priority, and can be used for managing the mobility of the terminal device. For example, the terminal device can preferably select or reselect a cell in which a high priority paging area is located when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source-side RAN network element may preferably consider supporting a neighboring RAN network element in which the high priority paging area is located as a RAN network element on the target side;
7. A public land mobile network identifier (Public Land Mobile Network, PLMN) corresponding to a network slice prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate an identifier of a PLMN that currently serves the terminal device , and / or a list of equivalent PLMN identifiers allowed to be accessed by the terminal device. Optionally, the PLMN identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be configured based on a network slice priority, and can be used for managing the mobility of the terminal device. For example, the terminal device can preferably select or reselect a cell in which a high priority PLMN is located when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source-side RAN network element may preferably consider supporting a neighboring RAN network element in which the high priority PLMN is located as a RAN network element on the target side; and
8. A network slice reselection policy: The network slice reselection policy can indicate whether a network device is allowed to always select one or more network slices for the terminal device, or whether the network device can select another network slice for the terminal device in a handover or cell reselection mode. For example, for a network slice indicated by at least one network slice identifier, an identifier of at least one network slice that can replace the network slice may be included. Optionally, the identifier among at least one slice
Petition 870190077990, of 12/08/2019, p. 48/83
43/69 network that can replace the network slice can be configured based on a priority. A criterion for determining a priority is not limited in this modality of this request. For example, sorting can be performed based on a network slice priority.
[0121] In 402, the RAN2 node responds to the RAN1 node with a first response request message, and the first response request message may include the following information:
1. A RAN2 node identifier: the RAN2 node identifier is used to uniquely identify the RAN2 node globally;
2. Information about a RAN2 node service cell and a corresponding neighbor cell for each service cell: for example, cell identities, physical cell identities, frequency information, tracking area identifiers or codes, and paging area corresponding to the corresponding service cell and neighboring cell for each service cell; a network slice identifier, physical access channel configuration, or network slice mobility parameter information that corresponds to a supported network slice, for example, a handover triggered change parameter, where the triggered change parameter by handover is used to indicate a limit to start preparing for handover from one cell to another cell;
3. A network slice identifier corresponding to a network slice that is prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate at least one network slice that is prohibited from being accessed or allowed to be accessed by the terminal device;
4. A cell identity corresponding to a network slice prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate at least one cell corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device. Optionally, the cell identity corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be configured based on a network slice priority, and can be used for managing mobility of the terminal device. For example, the terminal device can preferably select or reselect a cell
Petition 870190077990, of 12/08/2019, p. 49/83
44/69 high priority when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source side RAN network element may preferably consider supporting a neighboring RAN network element in which the high priority cell is located as a RAN network element on the target side;
5. An identifier or tracking area code corresponding to a network slice that is prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate at least one tracking area that is prohibited from being accessed or allowed to be accessed by the terminal device . Optionally, the tracking area code or identifier in the tracking area code or identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be configured based on a network slice priority, and can used for mobility management of the terminal device. For example, the terminal device can preferably select or reselect a cell in which a high priority tracking area is located when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source-side RAN network element may preferably consider supporting a neighboring RAN network element in which the high priority tracking area is located as a RAN network element on the target side;
6. A paging area identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate at least one paging area of a main network and / or access network corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device. Optionally, a paging area identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be configured based on a network slice priority, and can be used for managing the mobility of the terminal device. For example, the terminal device can preferably select or reselect a cell in which a high priority paging area is located when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a RAN network element on the source side
Petition 870190077990, of 12/08/2019, p. 50/83
45/69 may preferably consider supporting a neighboring RAN network element in which the high priority paging area is located as a RAN network element on the target side;
7. A public land mobile network identifier (Public Land Mobile Network, PLMN) corresponding to a network slice prohibited from being accessed or allowed to be accessed by the terminal device: used to indicate an identifier of a PLMN that currently serves the terminal device , and / or a stripe of equivalent PLMN identifiers allowed to be accessed by the terminal device. Optionally, the PLMN identifier corresponding to the network slice prohibited from being accessed or allowed to be accessed by the terminal device can be configured based on a network slice priority, and can be used for managing the mobility of the terminal device. For example, the terminal device can preferably select or reselect a cell in which a high priority PLMN is located when the terminal device is in an idle state or an inactive state. In a handover preparation stage, a source-side RAN network element may preferably consider supporting a neighboring RAN network element in which the high priority PLMN is located as a RAN network element on the target side; and
8. A network slice reselection policy: The network slice reselection policy can indicate whether a network device is allowed to always select one or more network slices for the terminal device, or whether the network device can select another network slice for the terminal device in a handover or cell reselection mode. For example, for a network slice indicated by at least one network slice identifier, an identifier of at least one network slice that can replace the network slice may be included. Optionally, the identifier of at least one network slice that can replace the network slice can be configured based on a priority. A criterion for determining a priority is not limited in this modality of this request. For example, sorting can be performed based on a network slice priority.
[0122] Optionally, when a situation of a network slice supported by the RAN1 node is changed, as shown in Figure 4, in 403, RAN1 can still send a second message request
Petition 870190077990, of 12/08/2019, p. 51/83
46/69 update to the RAN2 node. The second update request message includes information about the network slice that is changed, to instruct the RAN2 node to update information stored about the network slice supported by RAN1.
[0123] Optionally, at 404, the RAN2 node can still send a second update request confirmation message to the RAN1 node. The second update request confirmation message is used to indicate that RAN2 has received the second update request message. Optionally, if the RAN2 node fails to receive an update request message sent by the RAN1 node, the second update request confirmation message can carry a specific cause of failure. For example, the cause of the failure may include a configuration failure of a configuration corresponding to a specific network slice, or a plurality of or all network slices.
[0124] Therefore, the RAN1 node and the RAN2 node can exchange, in a manner described in Figure 4, network slice situations supported by the two RAN nodes. Likewise, any two access network nodes in a communications system can exchange, in the manner described in Figure 4, network slice situations supported by the two RAN nodes. In this mode, a RAN node currently accessed by a terminal device can obtain, in the mode described in Figure 4, a situation of a network slice supported by a RAN node to be accessed by the terminal device, in order to select a slice of appropriate network for the terminal device based on the situation of the network slice supported by the RAN node to be accessed.
[0125] Mode 2: a second network node is a RAN2 node, a second set of network slices is determined by a CN1 node and denoted as an NS Set2-CN1, and the CN1 node and a CN2 node they are the same main network node.
[0126] In this case, in 201, a RAN1 node sends a first message to the RAN2 node.
[0127] In 203, the RAN2 node sends a fourth message to the CN1 node.
[0128] In 204, the CN1 node sends a fourth response message to the RAN2 node.
Petition 870190077990, of 12/08/2019, p. 52/83
47/69 [0129] At 202, the RAN1 node receives a first response message sent by the RAN2 node.
[0130] The first message includes a network slice identifier corresponding to at least one network slice in a first set of network slices (that is, an NS Set1-RAN1). In 203, the RAN2 node sends the fourth message to CN1, and the fourth message includes a network slice identifier corresponding to at least one network slice (for ease of distinction and description, denoted as an NS Set1-RAN1- RAN2) in the first set of network slices. NS Set1-RAN1-RAN2 in the fourth message can include some or all of the network slices in NS Set1-RAN1. The fourth response message includes a network slice identifier corresponding to at least one network slice in the second set of network slices (i.e., an NS Set2-CN1).
[0131] Specifically, when RAN2 cannot determine which network slices should be accessed by the terminal device, RAN2 can send the fourth message to a main network node, that is, the CN1 node, in a communication system to the which RAN2 belongs to, and notify, using the fourth message, the CN1 node of the network slices that the terminal device wishes to access. In this mode, the CN1 node can redetermin, for the end device, based on the network slice identifier corresponding to at least one network slice in the first set of network slices (i.e. NS Set1-RAN1-RAN2), network slices to be accessed, that is, the second set of network slices. Based on the network slice identifier corresponding to at least one network slice in the first set of network slices (that is, NS Set1-RAN1-RAN2) included in the fourth message, CN1 can determine the second set of network slices network with reference to a factor such as a situation of a network slice supported by RAN2 and a load situation. For example, CN1 can determine that all network slices supported by RAN2 in NS Set1-RAN1-RAN2 form the second set of network slices, or can determine that some network slices supported by RAN2 in NS Set1-RAN1-RAN2 form the second set of network slices.
[0132] In other words, NS Set2-CN1 can include some or all of the network slices in NS Set1 -RAN1-RAN2. In other words, NS Set2CN1 can be a subset of NS Set1-RAN1-RAN2. A slice of network that
Petition 870190077990, of 12/08/2019, p. 53/83
48/69 is determined by the CN1 node and which is used for access by the terminal device can include some or all of the network slices in network slices which are selected for the terminal device and which are used for access by the terminal device. The CN1 node can filter some network slices based on the situation of the network slice supported by the RAN2 node.
[0133] Optionally, the CN1 node can alternatively reselect some or all of the network slices for the terminal device. In other words, NS Set2-CN1 may not be a subset of NS Set1RAN1-RAN2. NS Set2-CN1 can also include a network slice that is not included in NS Set1-RAN1-RAN2. The network slice that is included in NS Set2-CN1 but not included in NS Set1-RAN1-RAN2 can be a network slice that is reselected to the terminal device by CN1. Alternatively, CN1 can update information about some or all of the network slices on NS Set1-RAN1-RAN2.
[0134] Optionally, the fourth message can also include a temporary identifier corresponding to the terminal device, and the temporary identifier is used to search for context information stored on the terminal device by the CN1 node.
[0135] Optionally, the fourth message can also include service information corresponding to NS Set1-RAN1-RAN2. For specific content included in the service information corresponding to NS Set1-RAN1-RAN2, refer to the service information corresponding to NS Set1-RAN1 in the first message. For brevity, the details are not described in this report again.
[0136] Optionally, the fourth message can also include security information corresponding to NS Set1-RAN1-RAN2. For specific content included in the security information corresponding to NS Set1-RAN1-RAN2, refer to the security information corresponding to NS Set1-RAN1 in the first message. For brevity, the details are not described in this report again.
[0137] Optionally, in addition to the network slice identifier which corresponds to at least one network slice in the second set of network slices (that is, NS Set2-CN1) and which is reselected to the terminal device by the CN1, the fourth reply message may also include
Petition 870190077990, of 12/08/2019, p. 54/83
49/69 service information corresponding to at least one network slice in the second set of network slices (that is, NS Set2-CN1), for example, protocol data unit session information (Protocol Data Unit, PDU ) that are used to store session information, a session identifier, a carrier identifier, a QoS parameter, a tunnel identifier, an IP address of the transport bed (Internet Protocol, IP) and by the RAN2 node similar that are modified by CN1 for the terminal device.
[0138] Optionally, the fourth reply message may also include a first non-access layer message (Non Access Stratum, NAS) message. The first NAS message is an encapsulation message in the fourth reply message. The first NAS message is generated by the CN1 node, and the first NAS message includes the network slice identifier corresponding to at least one network slice in the second set of network slices (that is, NS Set2-CN1) . The first NAS message is used to instruct the terminal device to initiate a network slice reselection process. After receiving the fourth reply message including the first NAS message, RAN2 can transmit the first NAS message to RAN1, so that RAN1 can transmit the first NAS message to the terminal device. After receiving the first NAS message, the terminal device can initiate, based on the first NAS message, the network slice reselection process, which is alternatively referred to as a network slice update process. Optionally, the first NAS message can still be used to modify or disable the PDU session information initiated by the terminal device.
[0139] In 202, the RAN2 node sends the first reply message to the RAN1 node. The first response message includes the network slice identifier corresponding to at least one network slice in the second set of network slices (for ease of distinction and description, denoted as an NS Set2-CN1-RAN2). NS Set2-CN1-RAN2 can include some or all network slices in NS Set2-CN1. In other words, the RAN2 node can filter further, based on a factor, such as the situation of the network slice supported by the RAN2 node or the load situation, some network slices
Petition 870190077990, of 12/08/2019, p. 55/83
50/69 included in the first reply message.
[0140] Optionally, in addition to the network slice identifier corresponding to the network slice in NS Set2-CN1-RAN2, the first response message can also include at least one of the following:
service information allowed to be established and service information not allowed to be established that corresponds to at least one network slice in the second set of network slices.
[0141] Specifically, each network slice corresponds to the corresponding service information, such as carrier information, session information or flow information. RAN2 can only be allowed to establish service information corresponding to some network slices on NS Set2-CN1-RAN2, it can be allowed only to establish some service information corresponding to some network nodes on NS Set2-CN1-RAN2 or, it is likely that the service information corresponding to a network slice in NS Set2-CN1-RAN2 cannot be established. In this case, the first reply message can include service information allowed to be established and / or service information not allowed to be established which is / is corresponding to at least one network slice in NS Set2-CN1-RAN2.
[0142] Optionally, in Mode 2, the first message can be a handover request message, or it can be another message used for communication between a RAN node and another RAN node. Correspondingly, the first response message can be a handover request confirmation message, or it can be another message used for communication between the RAN node and the other RAN node.
[0143] Optionally, in Mode 2, the fourth message can be a handover request message, a path switching request message, or it can be another message used for communication between a RAN node and a CN node. Correspondingly, the fourth response message can be a handover request confirmation message, a path switch request confirmation message, or it can be another message used for communication between the RAN node and the CN node.
Petition 870190077990, of 12/08/2019, p. 56/83
51/69 [0144] Mode 3: a second network node is a CN1 node, a second set of network slices is determined by the CN1 node, the second set of network slices is denoted as an NS Set2-CN1, and CN1 and CN2 are the same main network node.
[0145] In this case, in 201, a RAN1 node sends a first message to the CN1 node.
[0146] In 202, the CN1 node responds to the RAN1 node with a first response message.
[0147] Specifically, in 201, the Cnode can receive the first message sent by the RAN1 node, where the first message includes a network slice identifier corresponding to at least one network slice in a first set of network slices (that is, an NS Set1 -RAN1). Based on NS Set1-RAN1, the CN1 node can determine the second set of network slices with reference to a situation of a network slice supported by a RAN2. For example, with reference to the status of the network slice supported by RAN2, the CN1 node can determine that all network slices supported by RAN2 in NS Set1-RAN1 form the second set of network slices, or it can determine that some slices networks supported by RAN2 in NS Set1-RAN1 form the second set of network slices. Optionally, the CN1 node can obtain in advance, using the method described in 303 in Figure 3, the situation of the network slice supported by the RAN2 node. The details are not described in this report again.
[0148] In other words, if the second network node that receives the first message sent by the RAN1 node is the CN1 node, the CN1 node can directly determine, based on the network slice identifier corresponding to at least one network slice in the first set of network slices (ie NS Set1-RAN1) included in the first message and with reference to the status of the network slice supported by the RAN2 node, the network slice identifier corresponding to at least one network slice in the second set of network slices (ie NS Set2-CN1).
[0149] Optionally, NS Set2-CN1 can include some or all of the network slices in NS Set1-RAN1. In other words, NS Set2-CN1 is a subset of NS Set1 -RAN1. A network slice that is determined by the CN1 node and that is used for access by a terminal device can include some
Petition 870190077990, of 12/08/2019, p. 57/83
52/69 or all network slices into network slices that are selected for the terminal device and that are used for access by the terminal device. The CN1 node can filter some network slices based on the situation of the network slice supported by the RAN2 node.
[0150] Optionally, the CN1 node can alternatively reselect some or all of the network slices for the terminal device. In other words, NS Set2-CN1 may not be a subset of NS Set1RAN1. NS Set2-CN1 can also include a network slice that is not included in NS Set1-RAN1. The network slice that is included in NS Set2-CN1 but not included in NS Set1-RAN1 can be a network slice that is reselected to the terminal device by CN1. Alternatively, CN1 can update information about some or all of the network slices on NS Set1-RAN1.
[0151] Optionally, in addition to a network slice identifier corresponding to each network slice in NS Set2-CN1, the first reply message can also include at least one of the following:
service information allowed to be established and service information not allowed to be established that corresponds to at least one network slice in the second set of network slices.
[0152] Specifically, each network slice corresponds to the corresponding service information, such as carrier information, session information or flow information. The first response message can include service information allowed to be established and / or service information not allowed to be established which is / is corresponding to at least one network slice in NS Set2-CN1.
[0153] Optionally, the first reply message can also include a first NAS message. The first NAS message is an encapsulation message in the first reply message. The first NAS message is generated by CN1, and the first NAS message includes the network slice identifier corresponding to at least one network slice in the second set of network slices (i.e., NS Set2-CN1). The first NAS message is used to instruct the terminal device to initiate a network slice reselection process. After receiving the first
Petition 870190077990, of 12/08/2019, p. 58/83
53/69 response message including the first NAS message, the RAN1 node can transmit the first NAS message to the terminal device. After receiving the first NAS message, the terminal device can initiate, based on the first NAS message, the network slice reselection process, which is alternatively referred to as a network slice update process. Optionally, the first NAS message can still be used to modify or disable PDU session information initiated by the terminal device.
[0154] Optionally, in Mode 3, the first message can be a handover request message, or it can be another message used for communication between a RAN node and a CN node. Correspondingly, the first response message can be a handover request confirmation message, or it can be another message used for communication between the RAN node and the CN node.
[0155] Optionally, in Mode 3, method 200 may also include the following steps.
[0156] In 211, the CN1 node sends a first notification message to the RAN2 node.
[0157] At 212, the RAN2 node sends a first notification confirmation message to the CN1 node.
[0158] The first notification message includes the network slice identifier corresponding to at least one network slice in the second set of network slices (that is, NS Set2-CN1), and the first notification confirmation message is used to notify the CN1 node that the RAN2 node received the first notification message sent by the CN1 node.
[0159] Optionally, the first notification message can be a handover request message, or it can be another message used for communication between the RAN node and the CN node. Correspondingly, the first notification confirmation message can be a handover request confirmation message, or it can be another message used for communication between the RAN node and the CN node.
[0160] Mode 4: a second network node is a CN1 node, a second set of network slices is determined by a CN2 node and denoted as an NS Set2-CN2, and CN1 and CN2 are different nodes from main network.
Petition 870190077990, of 12/08/2019, p. 59/83
54/69 [0161] In this case, in 201, a RAN1 node sends a first message to the CN1 node.
[0162] In 208, the CN1 node sends a seventh message to the CN2 node.
[0163] In 209, the CN2 node sends a seventh reply message to the CN1 node.
[0164] At 202, the RAN1 node receives a first response message sent by the CN1 node.
[0165] Specifically, if the RAN1 node and the RAN2 node do not belong to the same communications system, for example, if the RAN1 node belongs to a 4G communications system and the RAN2 node belongs to a communications system 5G, or if the RAN1 node belongs to a 5G communications system and the RAN2 node belongs to a 4G communications system, the CN1 node and the CN2 node are not the same main network node. After receiving the first message sent by the RAN1 node, the CN1 node can request the CN2 node to determine a network slice to be accessed by a terminal device. For a way of determining, by the CN2 node, a network slice to be accessed by the terminal device, it refers to the way of determining, by the CN1 node, a network slice to be accessed by the terminal device in Mode 3 or Mode 2. The details are not described in this report again.
[0166] Specifically, as a DCN identifier is an identifier used to identify an LTE system or an eLTE system, whether the communications system to which the CN1 node and CN2 node belong includes an LTE system or an eLTE system, an The function of mapping a network slice identifier to a DCN identifier on the CN1 node or on the CN2 node needs to be implemented. Whether the communications system to which the CN2 node belongs is an LTE system or an eLTE system, and the communications system to which the CN1 node belongs is a 5G system, and whether the first message includes a network slice identifier corresponding to at least one network slice in an NS Set1-RAN1, the CN1 node needs to map the network slice identifier to a DCN identifier. Specifically, the CN1 node maps the network slice identifier corresponding to at least one network slice in NS Set1-RAN1 to a corresponding DCN identifier
Petition 870190077990, of 12/08/2019, p. 60/83
55 / Q9 to at least one network slice in NS Set1-RAN1, select the CN2 node that corresponds to RAN2, and send the seventh message to the CN2 node in 208. The seventh message includes the DCN identifier corresponding to at least least one network slice in NS Set1-RAN1. Subsequently, the CN2 node determines a second set of network slices, that is, an NS Set2-CN2. In this case, CN2 needs to map a DCN identifier to a network slice identifier. Specifically, CN2 maps a DCN identifier corresponding to at least one network slice in the second set of network slices to a network slice identifier corresponding to at least one network slice in the second set of network slices. Then, in 209, the CN2 node sends a seventh response message to the CN1 node. The seventh response message includes the network slice identifier corresponding to at least one network slice in the second set of network slices.
[0167] Optionally, if the communications system to which the CN2 node belongs is a 5G system, and the communications system to which the CN1 node belongs is an LTE system or an eLTE system, and if the first message includes a DCN identifier corresponding to at least one network slice in NS Set1-RAN1, the CN1 node needs to map the DCN identifier to a network slice identifier. Specifically, the CN1 node maps the DCN identifier corresponding to at least one network slice in NS Set1RAN1 to the network slice identifier corresponding to at least one network slice in NS Set1-RAN1, selects the CN2 node that corresponds to RAN2, and sends the seventh message to CN2 in 208. The seventh message includes the network slice identifier corresponding to at least one DCN identifier in NS Set1-RAN1. Subsequently, the CN2 node determines the second set of network slices, that is, the NS Set2-CN2. In this case, CN2 needs to map a network slice identifier to a DCN identifier. Specifically, CN2 maps the network slice identifier corresponding to at least one network slice in the second set of network slices to a DCN identifier corresponding to at least one network slice in the second set of network slices. Then, in 209, the CN2 node sends a seventh response message to the CN1 node. The seventh response includes the DCN identifier corresponding to at least one network slice in the second set of network slices.
Petition 870190077990, of 12/08/2019, p. 61/83
56/69 [0168] Then, at 202, the CN1 node sends the first reply message to the RAN1 node. For specific content included in the first reply message, see Modality 1 for Modality 3. For brevity, the details are not described in this report again.
[0169] Optionally, the method in Mode 4 can also include the following steps.
[0170] 213: CN2 sends a second notification message to the RAN2 node.
[0171] 214: RAN2 sends a second notification confirmation message to CN2.
[0172] The second notification message is used to notify the RAN2 node that the CN2 node has reselected a network slice to be accessed for the terminal device, and the second notification confirmation message is used to indicate that the RAN2 received the second notification message.
[0173] Optionally, in Mode 4, the first message can be a handover request message, or it can be another message used for communication between a RAN node and a CN node. Correspondingly, the first response message can be a handover request confirmation message, or it can be another message used for communication between the RAN node and the CN node.
[0174] Optionally, in Mode 4, the seventh message can be a handover request message, or it can be another message used for communication between a CN node and a CN node. Correspondingly, the seventh response message can be a handover request confirmation message, or it can be another message used for communication between the CN node and the CN node.
[0175] In conclusion, with reference to the four preceding modalities, if the second node in the network that receives the first message is the RAN2 node, after receiving the first message sent by the RAN1 node, the RAN2 node can directly determine, based on the network slice identifier corresponding to at least one network slice in the first set of network slices (i.e. NS Set1-RAN1) included in the first message, the network slice identifier corresponding to at least one slice network on
Petition 870190077990, of 12/08/2019, p. 62/83
57/69 second set of network slices (ie NS Set2-RAN2) (Mode 1). Alternatively, RAN2 can request the main network node CN1 (in this case, RAN1 and RAN2 belong to the same communications system, and CN1 is CN2) in the communications system to which RAN2 belongs to determine the slice identifier of network corresponding to at least one network slice in the second set of network slices (ie NS Set2-CN1) (Mode 2).
[0176] Alternatively, if the second network node that receives the first message sent by the RAN1 node is the CN1 node, CN1 can directly determine, based on the network slice identifier corresponding to at least one network slice in the first set of network slices (ie NS Set1-RAN1) included in the first message, the network slice identifier corresponding to at least one network slice in the second set of network slices (ie NS Set2- CN1) (Mode 3). Alternatively, the CN1 node can request the main network node CN2 (in this case, RAN1 and RAN2 do not belong to the same communications system, and CN1 and CN2 are different main network nodes) in the communications system to which RAN2 belongs to determine the network slice identifier corresponding to at least one network slice in the second set of network slices (that is, NS Set2-CN2) (Mode 4).
[0177] It should be understood that the processes described in Modality 1 to Modality 4 can be performed during a cell handover process. For example, the first message can be a handover request message, the first response message is a handover request confirmation message, the fourth message is a handover request message or a path switch request message, and the fourth response message is a handover request confirmation message or a path switch request confirmation message. The processes can alternatively be carried out before the cell handover. This is not limited to these modalities of this application.
[0178] Optionally, after 202, as shown in Figure 2, method 200 can still include the following step.
[0179] In 205, the RAN1 node sends a second message to the terminal device.
Petition 870190077990, of 12/08/2019, p. 63/83
58/69 [0180] For Mode 1, the second message can include at least one of the following:
1. A target cell identity: used to identify the target cell;
2. A new temporary identifier of the terminal device: used to identify the terminal device in the target cell; and
3. A carrier configuration message: for example, Packet Data Convergence Protocol (PDCP), radio link control (Radio Link Control, RLC), Medium Access Control, MAC) or physical layer configuration information.
[0181] Optionally, for Mode 2, Mode 3 and Mode 4, in addition to at least part of the information included in Mode 1, the second message may also include the first NAS message. The first NAS message includes a network node that is determined by a primary network node and that is used for access by the terminal device. For example, for Mode 2 and Mode 3, the first NAS message includes the network slice identifier corresponding to at least one network slice in NS Set2-CN1; and for Mode 4, the first NAS message includes the network slice identifier corresponding to at least one network slice in NS Set2-CN2. The first NAS message is used to instruct the terminal device to initiate a network slice reselection process. After receiving the first NAS message, the terminal device can initiate, based on the first NAS message, the network slice reselection process, which is alternatively referred to as a network slice update process. Optionally, the first NAS message can still be used to modify or disable PDU session information initiated by the terminal device.
[0182] Optionally, the second message can be a handover instruction or another RRC message.
[0183] Optionally, if the second message includes the first NAS message, method 200 may also include the following step.
[0184] In 206, the terminal device sends a fifth message to the RAN2 node.
[0185] The fifth message includes a second NAS message. THE
Petition 870190077990, of 12/08/2019, p. 64/83
The second NAS message is generated by the terminal device based on the first NAS message, and the second NAS message includes the network slice identifier corresponding to at least one network slice in the second set of network slices. For example, for Mode 2 and Mode 3, the second NAS message includes the network slice identifier corresponding to at least one network slice in NS Set2-CN1; and for Mode 4, the second NAS message includes the network slice identifier corresponding to at least one network slice in NS Set2-CN2.
[0186] After the RAN2 node receives the second NAS message, in 207, the RAN2 node sends a sixth message to a corresponding main network node. The sixth message includes the second NAS message. In other words, the second NAS message can be transmitted to the corresponding main network node using the sixth message. For example, for Mode 2 and Mode 3, the RAN2 node can transmit the second NAS message to the CN1 node at 207; and for Mode 4, the RAN2 node can transmit the second NAS message to the CN2 node at 207.
[0187] Figure 5 is a schematic diagram of the interaction of a communication method 500, according to yet another modality of this request. As shown in Figure 5, method 500 includes the following steps.
[0188] In 501, a terminal device sends a first RRC message to a RAN node.
[0189] In 502, the RAN node sends a second RRC message to the terminal device.
[0190] At 503, the terminal device saves configuration information.
[0191] The first RRC message can be an RRC connection request, an RRC connection re-establish request, a complete RRC connection configuration message, or another message used for communication between the terminal device and the RAN node. Correspondingly, the second RRC message may be an RRC Connection Reject (RRC Connection Reject) message, an RRC Connection Release (RRC Connection Release) message, a MAC Control Element (Control Element, CE), or another message used for communication between
Petition 870190077990, of 12/08/2019, p. 65/83
60/69 the terminal device and the RAN node.
[0192] Specifically, the first RRC message can include a network slice identifier corresponding to at least one network slice in a first set of network slices, and is used to indicate a network slice that needs to be accessed by the device terminal.
[0193] Optionally, the first RRC message can still carry a NAS message that is used to initiate a network slice selection process or PDU session establishment.
[0194] Optionally, if the first RRC message includes network slice identifiers corresponding to a plurality of network slices, the terminal device can also indicate a priority of one or more network slices in the plurality of network slices.
[0195] Optionally, the first RRC message may also include a network slice reselection policy. For example, the network slice reselection policy can indicate whether a network device is allowed to always select one or more network slices for the terminal device, or whether the network device can select another network slice for the terminal device in a handover or cell reselection mode. For example, for a network slice indicated by at least one network slice identifier, an identifier of at least one network slice that can replace the network slice may be included. Optionally, the identifier of at least one network slice that can replace the network slice can be configured based on a priority. A criterion for determining a priority is not limited in this modality of this request. For example, sorting can be performed based on a network slice priority.
[0196] Optionally, the second RRC message may also include a network slice identifier corresponding to a network slice that is in a first set of network slices and for which the connection establishment is rejected or may include a cause of rejection corresponding to the network slice for which the connection establishment is rejected. For example, the cause of the rejection may be that the network slice to which the terminal device wishes to establish a connection is not available or does not exist on a RAN or CN.
[0197] Optionally, the second RRC message can still
Petition 870190077990, of 12/08/2019, p. 66/83
61/69 include information from the redirect cell. The redirect cell information is used to indicate information about a cell that is selected by the RAN node for the terminal device and that must be re-accessed by the terminal device, for example, a cell identity, a physical layer cell identity, or a carrier frequency. When the terminal device exits an RRC connection state and resumes cell selection, the terminal device can be redirected to a cell indicated by the redirection cell information.
[0198] Optionally, the second RRC message may also include information such as a cell identity allowed to be accessed or prohibited from being accessed, a tracking area identifier or code, a paging area identifier or a PLMN identifier of at least one network slice in the first set of network slices.
[0199] Optionally, the second RRC message can also include a Listen Before Talk, LBT parameter corresponding to at least one network slice in the first set of network slices. If the terminal device is redirected to a cell in an unlicensed spectrum, the second RRC message may also include at least part of the information such as a mapping relationship between a service and the LBT parameter, channel priority indication information preemption, a delayed access time and a containment window size.
[0200] Optionally, the second RRC message can also include a random access configuration parameter corresponding to at least one network slice in the first set of network slices, for example, available random access preamble information and location information of time-frequency resources of a physical random access channel resource (Physical Random Access Channel, PRACH).
[0201] Optionally, the second RRC message can also include redirect carrier information. Redirect carrier information is used to indicate a carrier frequency to which the terminal device needs to be redirected when the terminal device exits an RRC connection state and resumes cell selection, for example, a carrier frequency applicable to a 5G, eLTE, LTE
Petition 870190077990, of 12/08/2019, p. 67/83
62/69 or a similar communication system.
[0202] Optionally, the second RRC message can also include a frequency priority list, and the frequency priority list includes a priority applicable to cell reselection corresponding to a frequency of each access technology.
[0203] At 503, the terminal device can save at least part of the previous information included in the second RRC message, and at least part of the previous information is used for managing mobility of the terminal device in an RRC idle state, for example , cell selection or cell reselection.
[0204] Figure 6 is a schematic diagram of the interaction of a communication method 600, according to yet another modality of this request. As shown in Figure 6, method 600 includes the following steps.
[0205] In 601, a terminal device sends a third RRC message to a RAN node, where the third RRC message includes a network slice identifier corresponding to at least one network slice in a first set of network slices .
[0206] Optionally, the third RRC message can also carry a NAS message that is used to initiate a network slice selection or PDU session establishment process.
[0207] Optionally, if the third RRC message includes network slice identifiers corresponding to a plurality of network slices, the terminal device can also indicate a priority of one or more network slices.
[0208] Optionally, the third RRC message can also include a network slice reselection policy. The network slice reselection policy can indicate whether a network device is allowed to always select one or more network slices for the terminal device or whether the network device is allowed to select another network slice for the terminal device on a cell handover or reselection mode. For example, for a network slice indicated by at least one network slice identifier, an identifier of at least one network slice that can replace the network slice may be included. Optionally, the hair identifier
Petition 870190077990, of 12/08/2019, p. 68/83
63/69 minus a network slice that can replace the network slice can be classified based on a priority. A criterion for determining a priority is not limited in this modality of this request. For example, sorting can be performed based on a network slice priority.
[0209] In 602, the RAN node transmits, to a CN node, through the use of a first interface message, the NAS message carried in 601.
[0210] The first interface message is an interface message used for communication between the RAN node and the CN node.
[0211] In 603, the CN node sends a second interface message to the RAN node. The second interface message includes a network slice identifier corresponding to a network slice selected by the CN node for the terminal device, that is, a network slice identifier corresponding to at least one network slice in a second set of network slices. The second interface message is a message used for communication between the RAN node and the CN node.
[0212] Optionally, the second interface message can also include the network slice identifier corresponding to at least one network slice in the first set of network slices.
[0213] Optionally, the second interface message may also include information such as a cell identity allowed to be accessed or prohibited from being accessed, a tracking area identifier or code, a paging area identifier and a PLMN identifier of at least one network slice in the second set of network slices.
[0214] Optionally, the second interface message can be transmitted transparently by the RAN node to the terminal device in the form of a NAS message, and the NAS message can include some or all of the content of the second interface message.
[0215] For the information content included in the second interface message, it refers to the content included in the first reply message in Mode 3. The details are not described in this report again.
[0216] Optionally, if the RAN node does not support some or all of the network slices in the second set of network slices, in 604, the
Petition 870190077990, of 12/08/2019, p. 69/83
64/69
RAN can send a third interface message to the CN node. The third interface message is used to notify the CN node that the RAN node does not support some or all of the network slices in the second set of network slices that is determined by the CN node. Optionally, the third interface message can include a network slice identifier corresponding to a network slice that cannot be supported by the RAN2 node.
[0217] In 605, the RAN node sends a fourth RRC message to the terminal device. For the information content included in the fourth RRC message, it refers to the information content included in the second interface message. For the sake of brevity, the details are not described in this report again.
[0218] At 606, the terminal device can save at least a portion of the previous information included in the fourth RRC message, and at least a portion of the previous information is used for managing mobility of the terminal device in an RRC idle state, for example , cell selection or cell reselection.
[0219] The above describes in detail the modalities of the method of this application with reference to Figure 2 for Figure 6. The following describes in detail the modalities of the apparatus of this application with reference to Figure 7 for Figure 8. It should be understood that the apparatus modalities and method modalities are mutually corresponding. For similar descriptions, refer to the modalities of the method.
[0220] Figure 7 is a schematic block diagram of a communications device 700, according to one embodiment of this request. The communications apparatus 700 may correspond to (for example, it may be arranged on or is) the first node of the network, which is alternatively referred to as the first node of the access network (i.e., the RAN1 node), described in the method 200, or the RAN1 node described in method 300, or the RAN1 node described in method 400, or the RAN node described in method 500, or the RAN node described in method 600. In addition, device modules or units communications networks 700 are respectively configured to execute actions or processes executed by the first network node, which is alternatively referred to as the first access network node (that is, the RAN1 node), described in method 200, or by the RAN1 node described in method 300, either by the RAN1 node or the
Petition 870190077990, of 12/08/2019, p. 70/83
65/69
RAN2 described in method 400, either by the RAN node described in method 500, or by the RAN node described in method 600. In this report, to avoid repetition, the detailed description of the same is omitted.
[0221] In this embodiment of this request, the communications device 700 may include a processor and a transceiver, and the processor and transceiver are communicatively connected. Optionally, the communications device 700 also includes a memory and the memory and the processor are communicatively connected. Optionally, the processor, memory and transceiver can be communicatively connected. The memory can be configured to store an instruction and the processor is configured to execute the instruction stored in memory, in order to control the transceiver to send information or a signal.
[0222] A sending unit and a receiving unit of the communications device 700 shown in Figure 7 may correspond to the transceiver.
[0223] Figure 8 is a schematic block diagram of a communications device 800, according to one embodiment of this request. The communications apparatus 800 may correspond (for example, to be arranged on or is) the second network node described in method 200, such as the second access network node (i.e., the RAN2 node) or the first main network node (that is, the CN1 node), or the CN1 node described in method 300, or the RAN2 node described in method 400, or the CN node described in method 600. In addition, modules or communication device units 800 are respectively configured to perform actions or processing performed by the second network node described in method 200, such as the second access network node (i.e., the RAN2 node) or the first main network node (that is, the CN1 node), either by the CN1 node described in method 300, or by the RAN2 node described in method 400, or by the CN node described in method 600. In this report, to avoid repetition, detailed description of them is omitted.
[0224] In this embodiment of this request, the communications apparatus 800 may include a processor and a transceiver, and the processor and transceiver are communicatively connected. Optionally, the communications device 800 still includes a memory and the memory and processor are
Petition 870190077990, of 12/08/2019, p. 71/83
66/69 communicatively connected. Optionally, the processor, memory and transceiver can be communicatively connected. The memory can be configured to store an instruction and the processor is configured to execute the instruction stored in memory, in order to control the transceiver to send information or a signal.
[0225] A receiving unit and a sending unit of the communications device 800 shown in Figure 8 can correspond to the transceiver.
[0226] It should be noted that the modalities of the previous method can be applied to the processor or implemented by the processor. The processor can be an integrated circuit chip and has signal processing capability. In an implementation process, steps in the modalities of the preceding method can be implemented through the use of a logic integrated circuit to the hardware in the processor or use of an instruction in a software form. The processor can be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an array of field programmable ports (Field Programmable Gate Array , FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor can implement or execute the methods, steps and logic block diagram that are disclosed in the modalities of this request. The general purpose processor can be a microprocessor or the processor can be any conventional or similar processor. Steps in the methods disclosed with reference to the modalities of this order can be directly performed and performed using a hardware decoding processor, or can be performed and performed using a combination of hardware and software modules in the processor. decoding. A software module can be located on a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory or a register. The storage media is located in memory and the processor reads information in memory and
Petition 870190077990, of 12/08/2019, p. 72/83
67/69 implements, with reference to the processor hardware, the steps in the preceding methods.
[0227] It can be understood that the memory in the modalities of this application can be a volatile memory or a non-volatile memory or can include a volatile memory and a non-volatile memory. Non-volatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), a memory only programmable readout electrically erasable (Eletrically EPROM, EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM) used as an external cache. By way of illustrative rather than limiting description, many forms of RAM are available, for example, a static random access memory (Static RAM, SRAM), a dynamic random access memory (Dinamic RAM, DRAM), an access memory synchronous dynamic random (Synchronous DRAM, SDRAM), a synchronous dynamic random access memory with double data rate (Double Data Rate SDRAM, DDR SDRAM), an accentuated synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a memory of synchronous dynamic random access (Synchlink DRAM, SLDRAM), and a direct Rambus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described in this application includes, but is not limited to, these memories and any other appropriate type of memory.
[0228] It should be understood that the term “and / or” in this specification describes only one association relationship to describe associated objects and represents that three relationships can exist. For example, A and / or B can represent the following three cases: Only A exists, both A and B exist and only B exists. In addition, the “/” character in this specification generally indicates an “or” relationship between associated objects.
[0229] It should be understood that sequence numbers from previous processes do not mean sequences of execution in various modalities of this request. The sequences of execution of the processes must be determined, according to the functions and internal logic of the processes and must not be interpreted as any limitation in the
Petition 870190077990, of 12/08/2019, p. 73/83
68/69 implementation of the modalities of this request.
[0230] A person skilled in the art may be aware that, in combination with the examples described in the modalities disclosed in this specification, algorithm units and steps can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software, depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the functions described for each particular application, but it should not be considered that the implementation goes beyond the scope of the modalities of this application.
[0231] It can be clearly understood by a person skilled in the art that, for the purpose of a convenient and brief description, for a detailed operation process of the previous system, apparatus and unit, reference can be made to a corresponding process in the modalities of the previous method and the details are not described again in this report.
[0232] In the various modalities provided in this application, it should be understood that the system, apparatus and method disclosed can be implemented in other ways. For example, the mode of the apparatus described is merely an example. For example, the unit division is merely a logical function division, or it may be another division in the actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some characteristics may be ignored, or may not be realized. In addition, mutual couplings or direct couplings or communication connections shown or discussed can be implemented through the use of some interfaces. Indirect couplings or communication connections between devices or units can be implemented in electrical, mechanical or other forms. Units described as separate parts may or may not be physically separate and parts shown as units may or may not be physical units, may be located in one position, or may be distributed across a plurality of network units. Some or all of the units can be selected, according to the real requirements to obtain the objectives of the solutions of the modalities.
[0233] In addition, functional units in the modalities of this application
Petition 870190077990, of 12/08/2019, p. 74/83
69/69 can be integrated into a processing unit or each of the units can exist physically alone, or two or more units are integrated into one unit.
[0234] When functions are implemented as a functional software unit and sold or used as a standalone product, the functions can be stored on a computer-readable storage medium. Based on such an understanding, the technical solutions of this application essentially, or the contributing part to the prior art, or some of the technical solutions can be implemented in a form of a software product. The software product is stored on a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device or the like) to perform all or some of the steps in the methods described in the modalities of this request. The preceding storage media includes any media that can store program code, such as a USB flash drive, a removable hard drive, a read-only memory (Read-Only Memory, ROM), a random access memory , RAM), a magnetic disk or an optical disk.
[0235] The foregoing descriptions are merely specific implementations of the modalities of this application, but are not intended to limit the scope of protection of the modalities of this application. Any variation or substitution readily understood by a technician in the matter in the technical scope disclosed in the modalities of this order must fall within the scope of protection of the modalities of this order.

权利要求:
Claims (38)
[1]
1. Communication method, applied to a radio access network node, where the communication method comprises:
receive (301), by the radio access network node, a first network slice management request message sent by a main network node, wherein the first network slice management request message comprises a network identifier network slice of a network slice allowed to be used by a terminal device; and sending (302), through the radio access network node, a first network slice management request response message to the main network node.
[2]
Communication method according to claim 1, wherein the network slice identifier of the allowed network slice to be used by the terminal device is used to indicate at least one allowed network slice to be used by the terminal device.
[3]
Communication method according to claim 1 or 2, wherein the method further comprises:
send (303), through the radio access network node, a second network slice management request message to the main network node, wherein the second network slice management request message comprises information about a slice network supported by the radio access network node.
[4]
Communication method according to any one of claims 1 to 3, wherein the first network slice management request message is an initial UE context configuration message.
[5]
Communication method according to any one of claims 1 to 4, wherein the first network slice management request response message is used to indicate that the radio access network node accepts the first radio message. network slice management request sent by the main network node.
[6]
6. Communication method according to any of claims 1 to 4, wherein the first network slice management request response message is used to indicate that the access network node
Petition 870190077990, of 12/08/2019, p. 76/83
2/7 the radio rejects the first network slice management request message sent by the main network node, and the first network slice management request response message comprises a cause of rejection of the first management request message network slice.
[7]
Communication method according to any one of claims 3 to 6, wherein the second network slice management request message is used to request an establishment of an interface between the radio access network node and the main network node.
[8]
Communication method according to any one of claims 1 to 7, wherein the method further comprises:
receive (304), by the radio access network node, a second network slice management request response message sent by the main network node, wherein the second network slice management request response message is used to indicate that the primary network node has successfully received the second network slice management request message sent by the radio access network node.
[9]
9. Communication method, applied to a node of the main network, where the communication method comprises:
send (301), through the main network node, a first network slice management request message to a radio access network node, wherein the first network slice management request message comprises a slice identifier network of a network slice allowed to be used by a terminal device; and receiving (302), by the main network node, a first network slice management request response message sent by the radio access network node.
[10]
A communication method according to claim 9, wherein the network slice identifier of the allowed network slice to be used by the terminal device is used to indicate at least one allowed network slice to be used by the terminal device.
[11]
Communication method according to claim 9 or 10, further comprising:
receive (303), by the main network node, a second network slice management request message sent by the access network node
Petition 870190077990, of 12/08/2019, p. 77/83
3/7 the radio, in which the second network slice management request message comprises information about a network slice supported by the radio access network node.
[12]
Communication method according to any of claims 9 to 11, wherein the first network slice management request message is an initial UE context configuration message.
[13]
13. Communication method according to any of claims 9 to 12, wherein the first network slice management request response message is used to indicate that the radio access network node accepts the first radio message. network slice management request sent by the main network node.
[14]
Communication method according to any one of claims 9 to 12, wherein the first network slice management request response message is used to indicate that the radio access network node rejects the first network message. network slice management request sent by the main network node, and the first network slice management request response message comprises a cause of rejection of the first network slice management request message.
[15]
15. Communication method according to any of claims 11 to 14, wherein the second network slice management request message is used to request an establishment of an interface between the main network node and the network node radio access.
[16]
Communication method according to any one of claims 9 to 15, wherein the method further comprises:
send (304), through the main network node, a second network slice management request response message to the radio access network node, where the second network slice management request response message is used to indicate that the primary network node has successfully received the second network slice management request message sent by the radio access network node.
[17]
17. Communications device, applied to a radio access network node, where the communications device comprises:
Petition 870190077990, of 12/08/2019, p. 78/83
4/7 a receiving module, configured to receive a first network slice management request message sent by a main network node, where the first network slice management request message comprises a network slice identifier a network slice allowed to be used by a terminal device; and a sending module, configured to send a first network slice management request response message to the primary network node.
[18]
A communications apparatus according to claim 17, wherein the network slice identifier of the allowed network slice to be used by the terminal device is used to indicate at least one allowed network slice to be used by the terminal device.
[19]
19. A communications apparatus according to claim 17 or 18, wherein the sending module is additionally configured to send a second network slice management request message to the main network node, wherein the second network message network slice management request comprises information about a network slice supported by the radio access network node.
[20]
20. A communications apparatus according to any one of claims 17 to 19, wherein the first network slice management request message is an initial UE context configuration message.
[21]
21. Communications apparatus according to any one of claims 17 to 20, wherein the first network slice management request response message is used to indicate that the radio access network node accepts the first radio message. network slice management request sent by the main network node.
[22]
22. Communications apparatus according to any one of claims 17 to 20, wherein the first network slice management request response message is used to indicate that the radio access network node rejects the first network message. network slice management request sent by the main network node, and the first network slice management request response message comprises a cause of rejection of the first network slice request message
Petition 870190077990, of 12/08/2019, p. 79/83
5/7 network slice.
[23]
23. Communications apparatus according to any one of claims 19 to 22, wherein the second network slice management request message is used to request an establishment of an interface between the radio access network node and the main network node.
[24]
24. A communications apparatus according to any one of claims 17 to 23, wherein the receiving module is further configured to receive a second network slice management request response message sent by the main network node, wherein the second network slice management request response message is used to indicate that the primary network node has successfully received the second network slice management request message sent by the radio access network node.
[25]
25. Communications device, applied to a main network node, where the communications device comprises:
a sending module, configured to send a first network slice management request message to a radio access network node, where the first network slice management request message comprises a network slice identifier a network slice allowed to be used by a terminal device; and a receiving module, configured to receive a first network slice management request response message sent by the radio access network node.
[26]
26. A communications apparatus according to claim 25, wherein the network slice identifier of the allowed network slice to be used by the terminal device is used to indicate at least one allowed network slice to be used by the terminal device.
[27]
27. Communications apparatus according to claim 25 or 26, wherein the receiving module is additionally configured to receive a second network slice management request message sent by the radio access network node, in which the The second network slice management request message comprises information about a network slice supported by the radio access network node.
[28]
28. Communications apparatus, according to any of the
Petition 870190077990, of 12/08/2019, p. 80/83
6/7 claims 25 to 27, wherein the first network slice management request message is an initial UE context configuration message.
[29]
29. The communications apparatus according to any one of claims 25 to 28, wherein the first network slice management request response message is used to indicate that the radio access network node accepts the first radio message. network slice management request sent by the main network node.
[30]
30. Communications apparatus according to any one of claims 25 to 28, wherein the first network slice management request response message is used to indicate that the radio access network node rejects the first network message. network slice management request sent by the main network node, and the first network slice management request response message comprises a cause of rejection of the first network slice management request message.
[31]
31. Communications apparatus according to any one of claims 27 to 30, wherein the second network slice management request message is used to request an establishment of an interface between the main network node and the network node radio access.
[32]
32. Communications apparatus according to any one of claims 25 to 31, wherein the sending module is further configured to send a second network slice management request response message to the radio access network node , where the second network slice management request response message is used to indicate that the primary network node has successfully received the second network slice management request message sent by the radio access network node.
[33]
33. Communications apparatus, wherein the communications apparatus comprises a processor, and when a program instruction is executed by the processor, the communications apparatus performs the method as defined in any one of claims 1 to 16.
[34]
34. Communications device, in which the communications device is configured to perform the method as defined in any of the
Petition 870190077990, of 12/08/2019, p. 81/83
7/7 claims 1 to 16.
[35]
35. System chip, wherein the system chip comprises a processor, and when a program instruction is executed by the processor, the method as defined in any one of claims 1 to 16 is performed.
[36]
36. Computer program product, wherein the computer program product comprises a program instruction, and when the program instruction is directly or indirectly executed, the method as defined in any one of claims 1 to 16 is carried out.
[37]
37. Computer program storage media, wherein the computer program storage media comprises a program instruction, and when the program instruction is directly or indirectly executed, the method as defined in any of claims 1 to 16 is performed.
[38]
38. Communications system, wherein the communications system comprises the communications apparatus as defined in any one of claims 17 to 32 and claims 33 to 34, or the system chip as defined in claim 35, or the program product computer as defined in claim 36, or computer program storage media as defined in claim 37.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019015174A2|2020-03-24|COMMUNICATION METHOD AND COMMUNICATIONS APPARATUS

---

BR112019012530A2|2019-11-19|target cell and device access method

---

JP6769494B2|2020-10-14|Wireless terminals and base stations and their methods

---

BR112019019147A2|2020-04-14|user plan relocation techniques in wireless communication systems

---

JP6835102B2|2021-02-24|Base stations and wireless terminals and their methods

---

JP2021029055A|2021-02-25|Radio terminal and base station, and method therefor

---

RU2741946C1|2021-02-01|Radio terminal, a radio station, a core network node and a method therein

---

JP2020516184A|2020-05-28|Communication method, core network device and access network device

---

KR20200089316A|2020-07-24|Communication method and communication device

---

WO2015089849A1|2015-06-25|Method and apparatus for network switching

---

WO2016086409A1|2016-06-09|Access method, apparatus and system

---

BR112020002493A2|2020-08-04|base station and radiocommunication method

---

ES2882071T3|2021-12-01|Network node for use in a communication network, communication device and methods of operation thereof

---

CN111200850A|2020-05-26|Communication method and device

---

WO2016037642A1|2016-03-17|Handover from 3gpp to untrusted non-3gpp access based on measured communication path characteristics

---

BR112019027472A2|2020-08-25|wireless device and communication method

---

BR112020020055A2|2021-01-05|METHOD AND APPLIANCE FOR CARRIER CONFIGURATION

---

BRPI1012995B1|2021-07-06|METHOD, MOBILE STATION AND BASE STATION TO PROVIDE AN INDICATOR OF THE PRESENCE OF A FIRST ACCESS NETWORK THAT IS CAPABLE OF INTEROPERATING WITH A SECOND ACCESS NETWORK

---

WO2021062765A1|2021-04-08|Information transmission method and device

---

JP7004046B2|2022-01-21|Wireless terminals and base stations and their methods

---

WO2016106722A1|2016-07-07|Access method, apparatus and system

---

JP2022043257A|2022-03-15|Wireless terminal and its method

---

BR112020020219A2|2021-01-12|USER EQUIPMENT AND RELATED RADIOCOMMUNICATION METHOD AND NETWORK DEVICE

---

BR112020020501A2|2021-04-13|NEIGHBORHOOD RELATIONSHIP MAINTENANCE METHOD, FIRST NODE AND COMPUTER-READABLE STORAGE MEDIA

---

WO2017166291A1|2017-10-05|Communication method, terminal, base station, and mobility management equipment

同族专利:

---

公开号 | 公开日

---

US11051173B2|2021-06-29|

---

CN109474967A|2019-03-15|

---

JP6950141B2|2021-10-13|

---

CN110235471B|2022-01-11|

---

CA3051506A1|2018-08-02|

---

US20190349774A1|2019-11-14|

---

EP3905790A4|2021-11-03|

---

RU2758107C2|2021-10-26|

---

CN109474967B|2019-11-19|

---

CN108347751A|2018-07-31|

---

WO2018137684A1|2018-08-02|

---

JP2020505890A|2020-02-20|

---

RU2019126451A3|2021-06-02|

---

US20210321264A1|2021-10-14|

---

CN110235471A|2019-09-13|

---

EP3573375A4|2019-11-27|

---

EP3905790A1|2021-11-03|

---

CN108347751B|2021-08-03|

---

EP3573375A1|2019-11-27|

---

RU2019126451A|2021-02-26|

---

EP3573375B1|2021-03-17|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

CN102695248B|2011-03-22|2015-08-19|华为技术有限公司|Communication means under multi-mode networks, the network equipment and communication system|

---

US9515873B2|2013-03-12|2016-12-06|Dell Products L.P.|System and method for management of virtual sub-networks|

---

US10111163B2|2015-06-01|2018-10-23|Huawei Technologies Co., Ltd.|System and method for virtualized functions in control and data planes|

---

CN106341832B|2015-07-07|2020-11-06|中国移动通信集团公司|Network slice management and selection method, system, base station and route switching equipment|

---

US11202278B2|2015-11-10|2021-12-14|Nec Corporation|Communication method, mobile terminal, core network node, non-transitory computer readable recording medium storing program, and system for selecting network resource|

---

CN105516312B|2015-12-09|2019-02-22|重庆邮电大学|A kind of software defined network load balancing apparatus and method|

---

US20180352501A1|2015-12-29|2018-12-06|Telefonaktiebolaget Lm Ericsson |Method And Apparatus For Virtualized Network Service Provision|

---

CN108476547A|2016-01-15|2018-08-31|瑞典爱立信有限公司|Transmission communication device, reception communication device and the method thus executed in the context of network slice|

---

US10893405B2|2016-02-05|2021-01-12|Telefonaktiebolaget Lm Ericsson |Network nodes and methods performed therein for enabling communication in a communication network|

---

WO2017140341A1|2016-02-15|2017-08-24|Telefonaktiebolaget Lm Ericsson |Network nodes and methods performed therein for enabling communication in a communication network|

---

US11134487B2|2016-03-31|2021-09-28|Nec Corporation|SDN-based methods and apparatuses for providing TDD radio access network services|

---

WO2017171598A1|2016-04-01|2017-10-05|Telefonaktiebolaget Lm Ericsson |Handover in a wireless communication network with network slices|

---

US10681603B2|2016-04-22|2020-06-09|Telefonaktiebolaget Lm Ericsson |Method and network element for handover of user plane traffic|

---

CN106060900B|2016-05-13|2019-12-10|宇龙计算机通信科技有限公司|Access control method and device for network slice, terminal cell and SDN controller|

---

CN106210042B|2016-07-11|2019-06-18|清华大学|A kind of user service request selection method based on end to end network slice|

---

US20190174368A1|2016-07-22|2019-06-06|Nokia Technologies Oy|Security handling for network slices in cellular networks|

---

CN108702810B|2016-07-29|2021-09-14|Lg 电子株式会社|Method and arrangement for a first radio access network node|

---

CN106131891B|2016-08-30|2019-06-04|重庆邮电大学|A kind of resource mapping apparatus and method based on SDWN|

---

JP6951437B2|2016-11-11|2021-10-20|オッポ広東移動通信有限公司Ｇｕａｎｇｄｏｎｇ Ｏｐｐｏ Ｍｏｂｉｌｅ Ｔｅｌｅｃｏｍｍｕｎｉｃａｔｉｏｎｓ Ｃｏｒｐ．， Ｌｔｄ．|Wireless communication method, terminal equipment and network equipment|

---

CN109474967B|2017-01-25|2019-11-19|华为技术有限公司|Communication means and communication device|

---

EP3442293B1|2017-08-10|2020-07-15|Comcast Cable Communications, LLC|Activation of grant-free transmission|CN109474967B|2017-01-25|2019-11-19|华为技术有限公司|Communication means and communication device|

---

CN108632909B|2017-03-24|2019-08-23|电信科学技术研究院|A kind of QoS treating method and apparatus|

---

WO2018182224A1|2017-03-25|2018-10-04|엘지전자 주식회사|Access control method and device for supporting same|

---

CN108924849B|2017-04-01|2020-12-08|华为技术有限公司|Session connection establishing method and control plane network element|

---

EP3556146B1|2017-06-15|2021-03-03|ZTE Corporation|System and method for exchanging configuration information between two nodes in a wireless network|

---

CN109831807B|2017-11-23|2021-10-26|大唐移动通信设备有限公司|Indicating method of pilot frequency information, access network node and core network node|

---

CN111989979A|2018-02-25|2020-11-24|诺基亚通信公司|Method and system for controlling operation of a communication network to reduce latency|

---

CN110838927A|2018-08-15|2020-02-25|中国移动通信有限公司研究院|Slice mapping remapping method and access network element|

---

CN110972181B|2018-09-29|2021-09-07|华为技术有限公司|MDTmeasuring method, equipment and system|

---

CN110972107B|2018-09-29|2021-12-31|华为技术有限公司|Load balancing method and device|

---

CA3118227A1|2018-10-31|2020-05-07|Guangdong Oppo Mobile Telecommunications Corp., Ltd.|Protocol data unit session status indication method, terminal device, and storage medium|

---

CN111148187A|2018-11-02|2020-05-12|华为技术有限公司|Communication method and device|

---

US20220014938A1|2018-11-15|2022-01-13|Beijing Xiaomi Mobile Software Co., Ltd.|Method and device for using network slice|

---

CN111356205B|2018-12-21|2021-12-14|华为技术有限公司|Method and device for processing configuration information of public land mobile network|

---

CN111491338A|2019-01-28|2020-08-04|华为技术有限公司|Context storage method and device|

---

CN111586772B|2019-02-18|2021-06-22|华为技术有限公司|Communication method and device|

---

CN111726808A|2019-03-21|2020-09-29|华为技术有限公司|Communication method and device|

---

CN111866905A|2019-04-26|2020-10-30|华为技术有限公司|Communication method and related equipment|

---

CN112055423A|2019-06-06|2020-12-08|华为技术有限公司|Communication method and related equipment|

---

CN112243227A|2019-07-18|2021-01-19|华为技术有限公司|Method and device for data transmission under network slice architecture|

---

CN112469052A|2019-09-09|2021-03-09|中国移动通信有限公司研究院|Slice information reporting method and device|

---

WO2021077267A1|2019-10-21|2021-04-29|北京小米移动软件有限公司|Cell reselection method and apparatus, and communication device|

---

CN113141641A|2020-01-19|2021-07-20|中国移动通信有限公司研究院|Method and equipment for reselecting cell|

---

US11026149B1|2020-01-31|2021-06-01|Dish Wireless Llc|Systems and methods for reducing slice access failures|

---

WO2021168647A1|2020-02-25|2021-09-02|华为技术有限公司|Method for providing network slice, and communication apparatus|

---

WO2021109416A1|2020-04-20|2021-06-10|Zte Corporation|Ensuring service continuity in wireless communications|

---

CN113873581A|2020-06-30|2021-12-31|华为技术有限公司|Method and device for selecting cell|

---

CN113891427A|2020-07-01|2022-01-04|华为技术有限公司|Communication method and device|

---

CN113016210A|2020-08-06|2021-06-22|北京小米移动软件有限公司|Cell determination method and cell determination device|

---

WO2022038559A1|2020-08-19|2022-02-24|Telefonaktiebolaget Lm Ericsson |Differentiation support in paging procedures|

---

US11265220B1|2020-10-13|2022-03-01|Cisco Technology, Inc.|Auto switching for enterprise federated network slice|

法律状态:
2021-10-13| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

CN201710062740.1|2017-01-25|

---

CN201710062740.1A|CN108347751B|2017-01-25|2017-01-25|Communication method and communication device|

---

PCT/CN2018/074128|WO2018137684A1|2017-01-25|2018-01-25|Communication method and communication apparatus|

---